Fedora Account System
Red Hat Associate
Red Hat Customer
When using Fedora IoT raw images any symlinks created under /etc/systemd/system do not survive system reboots. The symlink is not present after the system is rebooted. Fedora IoT iso images appear to function as intended. Reproducible: Always Steps to Reproduce: 1. sudo systemctl set-default graphical.target 2. sudo systemctl reboot 3. ls -l /etc/systemd/system/default.target Actual Results: No symlink exists at /etc/systemd/system/default.target. Expected Results: lrwxrwxrwx. 1 root root 40 Nov 17 16:59 /etc/systemd/system/default.target -> /usr/lib/systemd/system/graphical.target Enabling the ignition-firstboot-complete.service and the coreos-ignition-write-issues.service rectifies this issue. * Does the service require post-rpm-installation configuration in order to be useful (for example, does it need manual edits to a configuration file)? No, it does not. * Does the service listen on a network socket for connections originating on a separate physical or virtual machine? No, it does not. * Is the service non-persistent (i.e. run once at startup and exit)? Yes. * What is the exact name (or names) of the systemd unit files to be enabled? ignition-firstboot-complete.service coreos-ignition-write-issues.service * Is this request for all Fedora deliverables or only for some Editions (list them)? Only Fedora IoT, specifically versions 41 and newer.
Pull requests made to fix this issue: https://src.fedoraproject.org/rpms/fedora-release/pull-request/366 https://src.fedoraproject.org/rpms/fedora-release/pull-request/367 https://src.fedoraproject.org/rpms/fedora-release/pull-request/368
Things look good here. I'll merge the MRs and get them built.
FEDORA-2025-c4345fed76 (fedora-release-41-31) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-c4345fed76
FEDORA-2025-8ebf68a4a2 (fedora-release-42-0.21) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-8ebf68a4a2
FEDORA-2025-8ebf68a4a2 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-8ebf68a4a2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-8ebf68a4a2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-c4345fed76 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-c4345fed76` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-c4345fed76 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-c4345fed76 (fedora-release-41-31) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.
Reopening and proposing as a freeze exception for Fedora 42 Beta
Proposed as a Freeze Exception for 42-beta by Fedora user djachimo using the blocker tracking app because: Proposing as a freeze exception for Fedora 42 beta, we would really appreciate it being included so IoT users can use ignition to set up their devices.
+3 in https://pagure.io/fedora-qa/blocker-review/issue/1779 , marking accepted.
FEDORA-2025-8ebf68a4a2 (fedora-release-42-0.21) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.