Bug 2348402

Summary:	Symlinks under /etc/systemd/system don't persist between reboots in Fedora IoT
Product:	[Fedora] Fedora	Reporter:	djachimo
Component:	fedora-release	Assignee:	Stephen Gallagher <sgallagh>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	42	CC:	alciregi, awilliam, fedoraproject, kevin, mboddu, miabbott, pbrobinson, pwhalen, samyak.jn11, sgallagh, thrcka, zbyszek
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	Unspecified
OS:	Linux
URL:	https://github.com/fedora-iot/iot-distro/issues/14
Whiteboard:	AcceptedFreezeException
Fixed In Version:	fedora-release-41-31 fedora-release-42-0.21	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-03-06 04:20:56 UTC	Type:	---
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:	2291264

Description djachimo 2025-02-26 14:42:48 UTC

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.

Comment 1 djachimo 2025-02-26 14:44:04 UTC

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

Comment 2 Stephen Gallagher 2025-02-28 15:14:12 UTC

Things look good here. I'll merge the MRs and get them built.

Comment 3 Fedora Update System 2025-02-28 15:35:52 UTC

FEDORA-2025-c4345fed76 (fedora-release-41-31) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-c4345fed76

Comment 4 Fedora Update System 2025-02-28 15:35:55 UTC

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

Comment 5 Fedora Update System 2025-03-01 01:54:46 UTC

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.

Comment 6 Fedora Update System 2025-03-01 03:12:00 UTC

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.

Comment 7 Fedora Update System 2025-03-02 02:19:39 UTC

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.

Comment 8 djachimo 2025-03-04 15:12:31 UTC

Reopening and proposing as a freeze exception for Fedora 42 Beta

Comment 9 Fedora Blocker Bugs Application 2025-03-04 15:14:10 UTC

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.

Comment 10 Adam Williamson (Red Hat non-Fedora) 2025-03-05 18:53:36 UTC

+3 in https://pagure.io/fedora-qa/blocker-review/issue/1779 , marking accepted.

Comment 11 Fedora Update System 2025-03-06 04:20:56 UTC

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.