Skip to content

test: prove native installer console entry and firmware fixture coverage #450

Open

Description

@castrojo

Parent

#448

What to prove

Before committing to exhaustive installer screenshots, demonstrate the new paths in real native QEMU/KVM and specify the smallest external console-driver interface on the existing Server dogfood harness. Test content belongs in testsuite; Server keeps QEMU/firmware/disks/boot/probe orchestration. Do not clone the harness or extend the unrelated desktop bootc e2e.yml.

Diskless interactive entry

The operator procedure mounts /run/bluefin/boot and invokes native systemd-sysinstall with the disk UKI and repart definitions. Existing dogfood-install.sh invokes it from an unattended probe without a TTY and pre-answers disk/erase/confirmation/registration. That does not prove a native diskless UI path.

Demonstrate a genuine console-attached invocation using existing systemd credential/probe mechanisms with the native command, or a verified operator login/provisioning path. State what temporary test authentication/console unit is used; do not disable production root locking globally. Drive native disk/keep-erase/firmware-registration/confirmation prompts. Respect the documented v261 nonempty-disk partition-device prerequisite.

Pre-Linux boot menu

The shipped loader.conf has timeout 3 and three UKI profiles. The Linux /dev/vcs mirror does not exist while systemd-boot is selecting a profile. Establish a firmware serial/framebuffer readiness signal and native keyboard navigation; prove explicit default/control-plane/node selection and capture. Do not count changing loader.conf's default as user UI navigation.

Firmware branches

  • Enforcing with Server keys: existing enrollment flow proves this.
  • No Secure Boot state: existing insecure firmware path is available; verify interactive warning/choices.
  • Server keys enrolled, Secure Boot off: enrolled-variable-store/insecure-firmware candidate must be checked for actual exposed state.
  • Foreign keys: the pinned Fedora RPM contains OVMF_VARS.secboot.fd, while CI extracts only blank OVMF_VARS.fd. Inspect trust contents and genuine reachability. Enforcing foreign firmware may reject the installer before Linux, so do not claim that warning exercised.
  • Setup Mode: upstream if-safe auto-enrolls in VMs. The user approved an explicitly declared disposable copy with upstream-supported secure-boot-enroll manual. Only loader configuration changes; signed installer binaries remain native/unchanged. Ordinary cases stay on unmodified images.

Mocked efivarfs, a scripted stand-in or invented fallback cannot establish E2E coverage. Any unreachable required branch remains a blocking open scope/fixture decision.

Shared input/capture contract

One driver owns the existing monitor endpoint. Observe/assert prompt, complete capture/release monitor access, send keys, assert transition. Serialize screendump and sendkey; no second controller/observer or second -monitor. Expose fresh screen/cursor state, the actual monitor path and guest lifecycle to the testsuite driver. QEMU socket paths must remain below the observed 108-byte UNIX path limit. Reuse testsuite's stdlib framebuffer conversion.

Existing evidence, not open assumptions

The hosted console step passed on 2026-10-11 in 76s (boot-test 28m41s/90m), and 2026-10-10 in 82s (boot-test 31m20s). Matching signed release passed the full four-boot scenario locally in 75.15s, exit 0. Existing hosted KVM and native console operation are demonstrated. Expanded cases, new fixtures and repeated screenshots still need proof.

Acceptance criteria

  • Real interactive diskless native entry and each exposed native prompt are demonstrated; no-TTY unattended probes are not counted.
  • Pre-Linux readiness/capture/navigation of each shipped profile is demonstrated with genuine key input.
  • Each Secure Boot inventory state has observed reachability/behavior or an explicit unresolved decision; no silent skips or mocked firmware coverage.
  • Serialized capture/input produces actual screenshots without dropping keystrokes or leaking secrets.
  • A minimal documented harness/driver contract preserves existing commands and ownership; testsuite's new-suite/consumer gate is already approved, but any new permissions/secrets still require approval.
  • Expanded hosted memory/disk/deadline use and screenshot repeatability are measured, not extrapolated from existing timings.
  • Throwaway probes are removed after evidence is retained; no installer implementation or release-policy change is smuggled into the feasibility work.

Blocked by

None for feasibility research. Stable long-paused USB screenshots depend on the separately filed userspace wait-online correction under the parent.

Activity

  1. added theissue type on Oct 11, 2026
  2. mrbobbytables commented on Oct 11, 2026

    @mrbobbytables
    Contributor

    When installing Bluefin Server, the operating system can run in several different security environments and boot modes. Before automated tests can take reliable screenshots of every installation screen, the team must decide how the test harness handles firmware setup and unattended installations across two specific scenarios:

    1. Foreign Secure Boot firmware enforcement: Standard test virtual machines can run with vendor Secure Boot certificates, but when foreign keys enforce signatures, UEFI firmware rejects the Bluefin installer before the operating system kernel boots. Maintainers need to decide whether the test matrix should verify firmware-level signature rejection or if native installer prompt coverage should be scoped strictly to firmware environments capable of executing the signed installer kernel.
    2. Interactive diskless console entry without root password exposure: Installing onto a local disk from a diskless network boot currently relies on unattended scripts without a terminal interface. Proving an interactive, console-attached installation path requires deciding on a temporary test credential or authenticated console unit to drive the prompts without weakening production root-account security.

    Until maintainers define the scope and fixture policies for foreign firmware validation and diskless console authentication, implementation of the expanded test matrix remains paused.

    — hive: backend=copilot model=gemini-3.8-flash


    🐝 Hive Agent: contributor | SHA: 9cf777e

  3. hivecommons-hive commented on Oct 11, 2026

    @hivecommons-hive
    Contributor

    What to reply

    • /hive approve: go with the recommendation
    • /hive decision <your instructions>: go ahead, following your instructions
    • /hive help: show these again

    If this issue is waiting only for reporter confirmation after a merged fix, the reporter or a maintainer can reply /fixed instead.

    Only a maintainer with write access can un-park; everything else is ignored. Full command reference: https://github.com/hivecommons/hive/blob/v5/src/docs/maintainer-commands.md.

  4. added
    stage/085-needs-decisionA human decision is owed: sentinel alert, hold/needs-decision label, human-only rule or parked issue
    stage/045-needs-decisionIssue parked on a person: needs-human or a maintainer decision is owed before the hive picks it up
    and removed
    stage/085-needs-decisionA human decision is owed: sentinel alert, hold/needs-decision label, human-only rule or parked issue
    on Oct 17, 2026
  5. jeefy commented on Nov 3, 2026

    @jeefy
    Collaborator

    Recommendation, reusing what scripts/dogfood-installer.sh already does instead of building a new console driver:

    Diskless interactive entry. Production root locking doesn't change. The diskless dogfood run creates a random password for that run, hashes it, and passes the hash in as passwd.hashed-password.root through the existing SMBIOS type=11 cred() helper (dogfood-diskless.sh:112, dogfood-installer.sh:253). The harness then:

    • logs in on tty1 with the QEMU monitor sendkey path (dogfood-installer.sh:434);
    • runs the documented systemd-sysinstall command from ddi-installer.md;
    • answers the disk, keep/erase, firmware-registration and confirmation prompts on the console, reading tty1 through the virtio mirror the installer test already uses.

    The plaintext password is only in that run's state directory, and CI hides it from logs with ::add-mask::. That is a real console-attached run of the native command, and the only test-only piece is one credential on one VM.

    Firmware fixtures. Firmware that holds only foreign keys (no Microsoft UEFI CA) can't boot a signed shim path we don't ship yet, so a full fixture would only show the expected refusal. Keep it out of scope until the shim is Microsoft-signed. If we want coverage now, add one cheap check: boot that firmware and assert that it refuses to boot, instead of a full installer pass.

    Pre-Linux boot menu. This stays at the QEMU monitor level (sendkey within the loader.conf timeout of 3, plus screendump), because /dev/vcs doesn't exist yet at that point.

  6. added
    triage/acceptedScope accepted; ready for work. Use `/triage accepted`.
    and removed
    needs-triageMissing required label matching ^triage/
    on Nov 5, 2026
  7. Danathar commented on Nov 9, 2026

    @Danathar
    Contributor

    /hive decision Go with @jeefy's 11-03 recommendation: reuse scripts/dogfood-installer.sh rather than a new console driver. Diskless interactive entry: a per-run random root password, hashed and passed as passwd.hashed-password.root via the existing SMBIOS type=11 cred() helper (production root locking unchanged); log in on tty1 via QEMU monitor sendkey, run the documented systemd-sysinstall command, answer the prompts on the console via the virtio tty1 mirror; mask the plaintext with ::add-mask::. Firmware fixtures: out of scope until the shim is Microsoft-signed; optionally add one check that foreign-keys-only firmware refuses to boot. Pre-Linux boot menu stays at QEMU monitor level (sendkey + screendump).

  8. added
    stage/010-actionableTriaged; eligible for the hive to pick up
    and removed
    stage/045-needs-decisionIssue parked on a person: needs-human or a maintainer decision is owed before the hive picks it up
    on Nov 9, 2026
  9. hivecommons-hive commented on Nov 9, 2026

    @hivecommons-hive
    Contributor

    Approved by @Danathar. Decision: Go with @jeefy's 11-03 recommendation: reuse scripts/dogfood-installer.sh rather than a new console driver. Diskless interactive entry: a per-run random root password, hashed and passed as passwd.hashed-password.root via the existing SMBIOS type=11 cred() helper (production root locking unchanged); log in on tty1 via QEMU monitor sendkey, run the documented systemd-sysinstall command, answer the prompts on the console via the virtio tty1 mirror; mask the plaintext with ::add-mask::. Firmware fixtures: out of scope until the shim is Microsoft-signed; optionally add one check that foreign-keys-only firmware refuses to boot. Pre-Linux boot menu stays at QEMU monitor level (sendkey + screendump).

    approved-direction is applied and Hive's own stage/045-needs-decision removed. Any hold label is left exactly as it was.

  10. hivecommons-hive commented on Nov 9, 2026

    @hivecommons-hive
    Contributor

    PR #644 covers this issue: #644

    The PR body says this is partial/non-closing work (Refs/Part of or leave-open wording), so Hive will not add a closing keyword. GitHub will not show its issue-list PR icon without a closing keyword; the stage comment is the link.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions