The differences we are seeing between a working Desktop ubuntu image with /var/log/installer/media-info 202408271 are that cloud-init published 24.2 via SRU to the newer Noble image
In that SRU was a shift to when cloud-init-hotplugd.socket and cloud- init-hotplugd.service units are ordered[1] The change added: - After=cloud-config.target to cloud-init-hotplugd.socket to allow starting hotplugd.socket earlier and - After=cloud-init.target to cloud-init-hotplugd.service to avoid attempting udev NIC hotplug events while cloud-init is still configuring the base instance. We'll need further investigation tomorrow to determine the ordering cycles we are seeingin Desktop images w/ NetworkManager-wait-online.service here, and why on first boot the systemd unit being deleted is dbus.service yet in ephemeral environment (before first boot) it happens to be cloud-init-hotplugd.service. [1] https://github.com/canonical/cloud-init/pull/5058 -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
