I'm building guest image for trove with dib on ubuntu jammy, and I have the same issue.
Great work by isolating the problem commit btw, saved a lot of time for me, thanks! Here is the workaround in bash which work for our env: # Workaround for the bug: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2113797 # TODO: remove the code when cloud-init package would be fixed export CLOUD_INIT_VERSION=$(dpkg-query -W -f='${Version}' cloud-init) if [ "$CLOUD_INIT_VERSION" = "25.1.2-0ubuntu0~22.04.1" ]; then mv /usr/lib/system/system/cloud-init* /lib/system/system/ mv /usr/lib/systemd/system-generators/cloud-init* /lib/systemd/system-generators/ systemctl enable cloud-init.service systemctl enable cloud-init-local.service systemctl enable cloud-config.service systemctl enable cloud-final.service fi (I've put the code in one of post-install script for dib) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2113797 Title: cloud-init 25.1.2 on Jammy not running on VM boot, systemd services disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2113797/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
