Bug 2259451 - Fedora 39 IoT Edition (aarch64): systemctl enable is not persistent, i.e. lost after reboot
Summary: Fedora 39 IoT Edition (aarch64): systemctl enable is not persistent, i.e. los...
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: zezere
Version: 39
Hardware: aarch64
OS: Linux
Target Milestone: ---
Assignee: Peter Robinson
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2024-01-21 21:32 UTC by wurstsemmel
Modified: 2024-04-06 20:16 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Type: ---
vasu3797: needinfo-

Attachments (Terms of Use)
Log from 'journalctl -b' (43.77 KB, text/plain)
2024-01-29 20:52 UTC, wurstsemmel
no flags Details

Description wurstsemmel 2024-01-21 21:32:59 UTC
systemctl enable does not enable the service persistent. It works fine until reboot, after reboot the service is disabled again.

Hardware: Raspberry Pi 4B

For more details please refer to Fedora Discussions: https://discussion.fedoraproject.org/t/fedora-39-iot-edition-systemctl-enable-rpm-ostreed-automatic-timer-disabled-after-reboot/101194

Reproducible: Always

Steps to Reproduce:
1. systemctl enable rpm-ostreed-automatic.timer
2. systemctl reboot
3. systemctl status rpm-ostreed-automatic.timer
Actual Results:  
rpm-ostreed-automatic.timer is disabled

Expected Results:  
rpm-ostreed-automatic.timer is enabled

It works as intended on x86_64 in Gnome Boxes (Fedora 39 Silverblue, Fedora 39 IoT Edition) and on bare metal x86_64 (Fedora 39 Workstation).

Comment 1 Zbigniew Jędrzejewski-Szmek 2024-01-29 10:59:08 UTC
Please paste:
1. output from the 'systemctl enable rpm-ostreed-automatic.timer' command
2. logs from the boot: 'journalctl -b'. If possible, add 'debug' to the kernel command line for the boot.

Comment 2 wurstsemmel 2024-01-29 20:52:07 UTC
Created attachment 2012648 [details]
Log from 'journalctl -b'

Comment 3 wurstsemmel 2024-01-29 21:11:06 UTC
Thank you very much for looking into this.

ad 1.
# systemctl is-enabled rpm-ostreed-automatic.timer
# systemctl enable rpm-ostreed-automatic.timer
Created symlink /etc/systemd/system/timers.target.wants/rpm-ostreed-automatic.timer → /usr/lib/systemd/system/rpm-ostreed-automatic.timer.
# systemctl is-enabled rpm-ostreed-automatic.timer
# systemctl reboot

ad 2.
# journalctl -b > boot.log
# systemctl is-enabled rpm-ostreed-automatic.timer

I attached boot.log after removing all entries from Nov 29. Unfortunately I do not know how to add 'debug' to the kernel command line.

Comment 4 Zbigniew Jędrzejewski-Szmek 2024-01-30 11:12:58 UTC
> Jan 29 21:34:10 rpi4 zezere-ignition[1323]: WARNING  : files: createResultFile: Ignition has already run on this system. Unexpected behavior may occur. Ignition is not designed to run more than once per system.

So it seems that the systems gets "reinitialized". I have no idea why.
Can ignition reset systemctl enablement symlinks?

I'll reassign this to zezere-ignition for comments.

Comment 5 wurstsemmel 2024-02-02 19:10:18 UTC
Some additional information which might help:

- A very similar case is described here: https://github.com/fedora-iot/iot-distro/issues/14
- I installed Fedora 39 IoT without zezere using arm-image-installer following this guide: https://www.redhat.com/sysadmin/fedora-iot-raspberry-pi

Note You need to log in before you can comment on or make changes to this bug.