Since I can't log into the guest due to the lack of proper init in the bad case I copied and mounted both daily images to check how they start fresh.
I see different cloud-init versions: good: 17.1-41-g76243487-0ubuntu1 bad: 17.1-53-ga5dc0f42-0ubuntu1 I see status and clean commands got added, but none of these should be the kill switch. I checked out the more reasonable changes in config and/or systemd files, but they all are of the same md5. Going slightly wider on what actually changed: http://paste.ubuntu.com/26169161/ The only change left that IMHO could cause this is the one in ds- identify. Now while I can't really use the new image, I can check what ds-identify left there on its first init (if anything). But that seems equal, the only thing that differs in: $ md5sum $(find /etc/cloud/ -type f | sort | xargs) is "/etc/cloud/build.info" which refers to the different image date. I fail to see why it didn't run so far :-/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737704 Title: Cloud-init seems not run on today's bionic images (20171211) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1737704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
