Bug 2391379
| Summary: | Minimal disk image boots to systemd-firstboot, not initial-setup as intended | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> |
| Component: | image-builder | Assignee: | Simon de Vlieger <cmdr> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | rawhide | CC: | cmdr, daan.j.demeyer, fedoraproject, go-sig, lnykryn, msekleta, osbuilders, pbrobinson, robatino, suraj.ghimire7, systemd-maint, yuwatana, zbyszek |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | aarch64 | ||
| OS: | Linux | ||
| Whiteboard: | AcceptedBlocker | ||
| Fixed In Version: | image-builder-33-1.fc43 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-08-30 18:13:58 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 2324223 | ||
|
Description
Adam Williamson
2025-08-27 21:44:04 UTC
Taking over this bug; I'll PR things to disable marking this image as being in firstboot so systemd doesn't reset /etc. To also have the information here: the ARM minimal images are (currently) built in a way that meets the preconditions for 'firstboot' behavior in systemd. This means that systemd will do a 'factory reset' (run preset-all --force) on first boot. Because ARM minimal images use mount units, they also have an early 'rw' sysroot. This combination means that a large chunk of /etc is being reset to presets. The presets do not include initial-setup. I have created an upstream PR at: https://github.com/osbuild/images/pull/1799 that disables the precondition for 'firstboot' behavior. This makes the image behave as expected again; /etc is not overwritten and thus initial-setup starts, systemd-firstboot does not (because it is based on the same precondition). Also note as part of the same issue we lost linux-firmware and grubby which causes network issues on some HW and means we can't update the kernel (it installs fine, but isn't set as default). Thanks Peter, I'll make sure the packages are included as part of the same update. FEDORA-2025-f8b43b5de3 (image-builder-33-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-f8b43b5de3 FEDORA-2025-30b4f2bc9f (image-builder-33-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-30b4f2bc9f FEDORA-2025-06c0d6aa7d (image-builder-33-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-06c0d6aa7d I've submitted updates to all active branches for this. The update includes both the fix for systemd-firstboot/initial-setup and the additional requested packages. To test this you can install the relevant build from bodhi and then build an image for Fedora 43: ``` sudo image-builder build --distro fedora-43 minimal-raw-xz sudo chown -R $USER:$USER fedora-43-minimal-raw-xz-x86_64/ unxz fedora-43-minimal-raw-xz/fedora-43-minimal-raw-zst-x86_64.raw.xz ``` Then use your favorite virtualisation tool on the disk image. Confirm that you end up in `initial-setup` instead of `systemd-firstboot` and that you can configure the system, and then login. Sorry, typo in the above snippet; the last line should read: ``` unxz fedora-43-minimal-raw-xz/fedora-43-minimal-raw-xz-x86_64.raw.xz ``` +4 in https://pagure.io/fedora-qa/blocker-review/issue/1887 , marking accepted blocker. Confirmed that it runs a initial-setup and looks fine. FEDORA-2025-30b4f2bc9f has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-30b4f2bc9f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-30b4f2bc9f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-f8b43b5de3 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-f8b43b5de3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-f8b43b5de3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-06c0d6aa7d has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-06c0d6aa7d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-06c0d6aa7d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-f8b43b5de3 (image-builder-33-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report. This fix also needs to be deployed to infra to complete the fix. I believe the relevant tags inherit from the compose tag so the update should appear in the buildroot automatically, like it already did for rawhide. (In reply to Simon de Vlieger from comment #17) > I believe the relevant tags inherit from the compose tag so the update > should appear in the buildroot automatically, like it already did for > rawhide. Cool, wasn't sure if it was deployed in a buildroot or had to be deployed to infra explicitly, thanks for the confirmation. FEDORA-2025-06c0d6aa7d (image-builder-33-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-30b4f2bc9f (image-builder-33-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report. |