Repository navigation
bootupd CI: composefs e2e boot broken by bootc composefs.digest= karg vs 1.16 initramfs #34
Description
coreos/bootupd CI bootc-e2e (ubuntu-24.04, 0, 10) composefs UEFI boot now fails in the initrd: initrd-switch-root.service fails and it drops to emergency mode; bootc-root-setup.service never runs.
Cause: the test image upgrades bootc from bootc main (now 202609250143.gf62a0ed3a3; the last green run on 9/21 used g65321aed79) but keeps the centos-bootc stream10 initramfs (bootc 1.16.13). Since bootc ba10fb16fc (Generate both V1 and V2 EROFS images on install), install writes only composefs.digest=v1-sha512-12:... instead of composefs=..., and the 1.16.13 bootc-root-setup.service has ConditionKernelCommandLine=composefs, so it is skipped. The new unit also accepts composefs.digest, but that initramfs is not regenerated.
Evidence: failing https://github.com/coreos/bootupd/actions/runs/36194645623/job/108275112081 (cmdline has composefs.digest=, no bootc-root-setup) vs green main https://github.com/coreos/bootupd/actions/runs/35635888015/job/106453076598 (composefs=, bootc-root-setup ran). First seen on coreos/bootupd#1163, which does not touch install.
Q: should bootc keep writing composefs= on install for older initramfs (compat), or should bootupd CI regenerate the initramfs after upgrading bootc?
Activity
cgwalters-bot commentedon Oct 17, 2026
Board scheduler: no plan. A triage run is asked whether this is done; it answers here. Delete this comment to ask again.
github-actions commentedon Oct 17, 2026
✅ dispatch ended well. Result: #34 (comment)
cgwalters-bot commentedon Oct 17, 2026
Conclusion: partly fixed, but the rest can't be planned yet. The fix the issue asks for has merged in coreos/bootupd. The composefs boot that the issue says is broken is still skipped on stream10 in bootupd CI, so nothing shows it passes. Re-enabling it is a one-line change in
coreos/bootupd, and that repository isn't in the dispatch bounds (.github/agentic-job/dispatch.tomlonly listscgwalters-forge/*). So I can't write an implement plan for it that would be accepted.What landed
97658ead): "ci: Regenerate the initramfs after installing bootc from copr". It runsdracut --forcein theDockerfileafterdnf install bootc, so the initramfs'sbootc-root-setup.servicealso starts oncomposefs.digest=. This is the second option in the issue's question. The PR says a newer bootc with an older initramfs isn't supported. Nothing in bootc changed to writecomposefs=again for older initramfs; I found no such PR in bootc-dev/bootc since 26 Sep. The PR author booted composefs UEFI tologin:on a devspace, but only for stream10 x86_64.bootc-e2e (ubuntu-24.04, 0, 10)passes: run 38204910006, job 114666138189. The log shows thedracut --force --kver 6.12.0-275.el10...step.What's left
6969be576c"ci: Skip composefs tests for C10S") addedif [[ "${{ matrix.stream }}" != "10" ]]aroundtest-uefi-vm-boot.sh "$IMG_NAME" "composefs"in.github/workflows/ci.yml. Because of that, the green stream10 job above only boots ostree. That skip is still on main.(ubuntu-24.04, 0, 10)and(ubuntu-24.04-arm, 0, 10)boot composefs to login. That's a PR to coreos/bootupd.(ubuntu-24.04-arm, 1).dnf download grub2-efi-aa64-ccfrom Fedora ELN failed after a mirror returned HTTP 500. It isn't this issue (ci: Fetch grub-cc from Fedora Koji bootc-dev/bootc#2575 moved bootc's own CI to fetch grub-cc from Koji).Needed before it can be planned: a decision from cgwalters on either
coreos/bootupdto the dispatch bounds so an implement run can open the PR above, orcgwalters-bot commentedon Oct 17, 2026
The fix this issue asked for merged as coreos/bootupd#1168, which regenerates the initramfs after installing bootc, and the board already shows Done. The one remaining step is to re-enable the stream10 composefs boot leg in bootupd CI. That change is in coreos/bootupd, which is outside the dispatch bounds, and it does not gate the composefs-stable epic. See #34 (comment). Reopen this if the operator wants it tracked here.