Hello @Timo! Thank you so much for the quick turnaround on this issue. I also tested building a fresh Jammy image with the new package and it deploys fine w/o any issues now.
Output snippet from the build log: cloudimg.image.qemu.cloudimg: Get:1 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 cloud-init all 24.4.1-0ubuntu0~22.04.2 [566 kB] cloudimg.image.qemu.cloudimg: Preconfiguring packages ... cloudimg.image.qemu.cloudimg: Fetched 566 kB in 1s (730 kB/s) cloudimg.image.qemu.cloudimg: (Reading database ... 63167 files and directories currently installed.) cloudimg.image.qemu.cloudimg: Preparing to unpack .../cloud-init_24.4.1-0ubuntu0~22.04.2_all.deb ... cloudimg.image.qemu.cloudimg: Unpacking cloud-init (24.4.1-0ubuntu0~22.04.2) over (24.4.1-0ubuntu0~22.04.1) ... cloudimg.image.qemu.cloudimg: Setting up cloud-init (24.4.1-0ubuntu0~22.04.2) ... cloudimg.image.qemu.cloudimg: Processing triggers for man-db (2.10.2-1) ... cloudimg.image.qemu.cloudimg: Processing triggers for rsyslog (8.2112.0-2ubuntu2.2) ... cloudimg.image.qemu.cloudimg: NEEDRESTART-VER: 3.5 cloudimg.image.qemu.cloudimg: NEEDRESTART-KCUR: 5.15.0-134-generic cloudimg.image.qemu.cloudimg: NEEDRESTART-KSTA: 0 ==> cloudimg.image.qemu.cloudimg: + apt-get autoremove --purge -yq cloudimg.image.qemu.cloudimg: Reading package lists... cloudimg.image.qemu.cloudimg: Building dependency tree... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2100963 Title: cloud-init fails with MAAS since Feb 4 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2100963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
