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.
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.
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: g76243487- 0ubuntu1 ga5dc0f42- 0ubuntu1
good: 17.1-41-
bad: 17.1-53-
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: build.info" which refers to the different image date.
$ md5sum $(find /etc/cloud/ -type f | sort | xargs)
is "/etc/cloud/
I fail to see why it didn't run so far :-/