Repository navigation
Conversation
Every headless first boot of Bluefin Server stalls forever on an interactive prompt. systemd-homed-firstboot.service is ConditionFirstBoot=yes, runs `homectl firstboot --prompt-new-user` with StandardInput=tty, and orders itself Before=first-boot-complete.target. With no operator at the console the boot transaction never completes, so k0s never starts. The DDI element already masked systemd-firstboot.service "to prevent interactive prompts on headless first boot"; that mask was simply incomplete. homed ships its own wizard as a separate unit, pulled in via WantedBy=systemd-homed.service, and was never masked. Mask it alongside systemd-firstboot.service and widen the comment and the ddi-installer skill to name both units and the reason. Assisted-by: Claude Opus 4.6 via GitHub Copilot Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
CI evidence on this branch: the prompt is goneRun 35382696469: The
So masking |
|
Author note — I cannot review my own PR, so recording the evidence and the audit. This is a product bug, not a CI bug. Every headless first boot of Bluefin Server currently stalls forever. The existing mask next to it covers Premise verified three ways before changing anything:
Confirmed fixed by a subsequent run. With the unit masked, the wizard is gone (occurrences 1 -> 0) and the installed system boots clean through to Why in the image and not the smoke test. Masking it only in the Justfile would have turned Audit of other units that could block a headless boot the same way. Enumerated every unit with The mask is safe because the unit is reached via Context: this is the third independent blocker on
|
|
Runtime evidence: I built a throwaway integration of #173 + #181 + #186 and ran it through CI. Run 35388029502 is GREEN — Decisive serial console lines: and host-side: Three independent blockers, all required; any two still fail:
The marker is not a false positive. At t=38s and t=69s the loop was awake with k0s active and 10 pods present, but The deadline is not a problem. Readiness is reached at t=89s against a 900s budget — roughly 10x headroom. No change to Caveat, stated plainly: the run exercised the The integration branch was a throwaway: no temporary PR was opened, and the branch and worktree are deleted. Neither #173's nor #181's diff or head was touched by any of it. |
|
Thanks for the review. No findings were raised, so no code changes were needed. |
|
Closing as superseded by #210, which lands the identical change plus the matching test and docs update. Both wizards are now masked in Same reasoning as your description: both are |
This is a product bug, not a CI bug
Every headless first boot of Bluefin Server hangs indefinitely on an interactive
prompt — PXE, datacenter provisioning, sysupdate-driven reinstall, and the QEMU
smoke test alike.
systemd-homed-firstboot.serviceis:ConditionFirstBoot=yesExecStart=homectl firstboot --prompt-new-user --prompt-shell=no --prompt-groups=no --mute-console=yesStandardInput=tty/StandardOutput=ttyBefore=systemd-user-sessions.service first-boot-complete.targetWith nobody at the console, the boot transaction never completes and k0s never
starts. The fix belongs in the image, not in the smoke test: masking it only in
the
Justfilewould make CI green while every real headless install still hangs.elements/oci/bluefin-server-ddi.bstalready maskedsystemd-firstboot.servicewith the comment "Mask systemd-firstboot to prevent interactive prompts on
headless first boot". That mask was incomplete, not a deliberate carve-out:
homed ships its own first-boot wizard as a separate unit, pulled in via
WantedBy=systemd-homed.service, and it was never masked.Evidence
Integration run
35375246792
(
tmp/integration-173-181, a throwaway integration of #173 + #181):buildsucceeded, the
/varemergency-mode failure was gone (zeroDependency failed,zero
emergency mode), butinstaller-teststill timed out at 900s and theserial log ends at:
That prompt string comes from
homectl firstboot, confirming the unit ships andruns in the built image. FSDK 26.08's systemd is built with
-Dfirstboot=trueand all of homed's dependencies (
openssl,cryptsetup,util-linux-libfdisk,linux-pam) enabled.This is the third independent blocker on
installer-test, alongside#173 (the
/varfix) and #181 (the readiness gate). All three must land forinstaller-testto pass; none of them subsumes the others.Change
systemd-homed-firstboot.serviceis reached throughWants=, notRequires=,so masking it cannot fail the boot.
The existing contract test
test_ddi_generates_module_indexes_for_runtime_filesystem_driversalready asserted the
systemd-firstboot.servicemask; it now asserts both.docs/skills/ddi-installer.mdcarried the canonical statement of this fact andwas widened to name both units.
Audit: other units that could block a headless boot on tty input
Every unit in the image's systemd with
StandardInput=tty*was checked. Only thetwo first-boot wizards are genuine blockers. Judged safe to leave:
getty@,serial-getty@,console-getty,container-getty@breakpoint-pre-{udev,mount,basic,switch-root}systemd.break=cmdline argumentemergency,rescuedebug-shellsystemctl enablesystemd-storagetmsystemd-sysinstallConditionFirstBoot; only started bysystem-install.targetin the live installer, where it is the intended interactive flowNothing in
files/defines a unit withStandardInput=,ConditionFirstBoot=,or a
--promptExecStart.Verification
just validate— exit 0python3 -m pytest tests/unit/test_installer_contract.py -q— 8 passedpython3 .github/scripts/docs-checks.py— passedAssisted-by: Claude Opus 4.6 via GitHub Copilot