I have also confirmed that livecd-rootfs doesn't appear to have changed their "drop-in" of cloud-init.service files https://git.launchpad.net/ubuntu/+source/livecd-rootfs/tree/live- build/functions#n1060 so it's unlikely a new cloud-init issue introduced across an SRU boundary.
This makes me think something has changed in systemd or NetworkManager units and ordering on Noble recently to cause this recent issue or something that the OEM environment is installing that is causing this issue: From the looks of the var/log/apt/term.log nvidia-kernel-common-550 package seems to be installing a few systemd units Created symlink /etc/systemd/system/systemd-hibernate.service.wants/nvidia-hibernate.service → /usr/lib/systemd/system/nvidia-hibernate.service.^M^M Created symlink /etc/systemd/system/systemd-suspend.service.wants/nvidia-resume.service → /usr/lib/systemd/system/nvidia-resume.service.^M^M Created symlink /etc/systemd/system/systemd-hibernate.service.wants/nvidia-resume.service → /usr/lib/systemd/system/nvidia-resume.service.^M^M Created symlink /etc/systemd/system/systemd-suspend.service.wants/nvidia-suspend.service → /usr/lib/systemd/system/nvidia-suspend.service.^M^M I'm guessing we want to look at those and their ordering (systemctl show -p Before,After nvidia-resume.service and nvidia-suspend.service as that seems to be the only thing outside of stock Desktop images that is altering systemd unit boot order -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2081124 Title: systemd service dependency loop between cloud-init, NetworkManager and dbus To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2081124/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
