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).
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.
Created attachment 2012648 [details] Log from 'journalctl -b'
Thank you very much for looking into this. ad 1. # systemctl is-enabled rpm-ostreed-automatic.timer disabled # 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 enabled # systemctl reboot ad 2. # journalctl -b > boot.log # systemctl is-enabled rpm-ostreed-automatic.timer disabled 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.
> 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.
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
This message is a reminder that Fedora Linux 39 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '39'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 39 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26. Fedora Linux 39 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.