Adjusts the systemd unit files avoid a cyclical dependency on services like auditd.
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2025-39306e86fdPlease log in to add feedback.
This update has been submitted for testing by jcline.
This update's test gating status has been changed to 'ignored'.
It looks like this fix doesn't work in Rawhide testing :(
https://openqa.fedoraproject.org/tests/3668307#step/base_services_start/7
This update has been pushed to testing.
So I am testing with
Fedora-Cloud-Base-AmazonEC2.aarch64-Rawhide-20250826.2which has cloud-init-25.2-4.fc44.noarch and it is a bit better, at least that it how it looks like from our integration tests, but I still see some connection issues wheresshddoes not start.In journal I see for example (here
sshddid actually start):Aug 27 02:19:35 localhost systemd-journald[503]: Runtime Journal (/run/log/journal/ec25151dd390da871f0b77c632b18850) is 8M, max 75.6M, 67.6M free. Aug 27 02:19:35 localhost systemd[1]: [🡕] sysinit.target: Found ordering cycle: systemd-update-utmp.service/start after auditd.service/start after cloud-init-local.service/start after cloud-> Aug 27 02:19:35 localhost systemd[1]: [🡕] sysinit.target: Job systemd-update-utmp.service/start deleted to break ordering cycle starting with sysinit.target/start Aug 27 02:19:35 localhost systemd[1]: [🡕] sysinit.target: Found ordering cycle: auditd.service/start after cloud-init-local.service/start after cloud-init-main.service/start after dbus.socke> Aug 27 02:19:35 localhost systemd[1]: [🡕] sysinit.target: Job auditd.service/start deleted to break ordering cycle starting with sysinit.target/start
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
jcline edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by jcline.
Thanks for testing it.
I've made a further tweak to the systemd unit patch with cloud-init-25.2-5 - I had ended up reintroducing its dependency on
After=sysinit.targetby pulling in the upstream'sAfter=dbus.socketdependency it has for RHEL and its derivatives - I think that will be something that will break RHEL in the future whenever it pulls in the change that broke Fedora, so someone from Red Hat should probably investigate that (I don't know if the current RHEL version does in fact need dbus.socket to be available)The revised version looks good in openQA testing I hacked up last night.
https://openqa.stg.fedoraproject.org/tests/5290811
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
The fix for BZ#2390898 seem to be about installability tests right, and from F44 that part seems to be resolved.
Maybe there is still some other issues remaining for sshd, but this update should be fine to integrate as-is @mvadkert. At the very least it doesn't seem to create new issues.
mvadkert's comment was on the initial version of this update which didn't manage to fix the ordering cycle issue.
This update has been submitted for stable by adamwill.
There is an ongoing freeze; this will be pushed to stable after the freeze is over.
This update has been pushed to stable.