[Bug 1563951] Re: Cloud-init does not initialize systemd machine id

2016-04-13 Thread Oliver Grawert
you might want to consider an initrd script that kicks in after mounting the rootfs but before running run-init to switch to the filesystem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563951 Title

[Bug 1563951] Re: Cloud-init does not initialize systemd machine id

2016-04-05 Thread Scott Moser
Greg, So digged a bit further, it seems that the ubuntu images do the right thing in that /etc/machine-id is not present in the image itself. I suspect your instances that you noticed this on were snapshotted from a once-booted instance or in some other way booted. If that is the case, it would

[Bug 1563951] Re: Cloud-init does not initialize systemd machine id

2016-04-05 Thread Scott Moser
Yeah, likely this happens to early in boot for cloud-init to affect. I've marked livecd-rootfs as a target, which is (i think) proper for changing the images themselves. ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu)

[Bug 1563951] Re: Cloud-init does not initialize systemd machine id

2016-04-05 Thread Greg Fefelov
(systemd generates a random machine-id if there is no /etc/machine-id whatsoever.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563951 Title: Cloud-init does not initialize systemd machine id To

[Bug 1563951] Re: Cloud-init does not initialize systemd machine id

2016-04-05 Thread Greg Fefelov
Unfortunately, systemd reads /etc/machine-id prior to launching any tasks, so I think this not a cloud-init issue. The proper solution, I guess, would be to delete /etc/machine-id before making an ami out of a running instance. Sorry to bother :( -- You received this bug notification because you

[Bug 1563951] Re: Cloud-init does not initialize systemd machine id

2016-04-04 Thread Scott Moser
Is it enough during boot to just: rm /etc/machine-id echo "" > /etc/machine-id ? Note that systemd-firstboot.service is not currently in ubuntu (xenial) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bu

[Bug 1563951] Re: Cloud-init does not initialize systemd machine id

2016-04-04 Thread Scott Moser
Hi, This does look like it would be useful. It seems like the thing I should do is : once per instance remove /etc/machine-id and run systemd-machine-id-setup Ideally i think is that any system where the instance-id is a uuid, we could just populate /etc/machine-id with that instance-id. What w

[Bug 1563951] Re: Cloud-init does not initialize systemd machine id

2016-03-30 Thread Scott Moser
** Changed in: cloud-init (Ubuntu) Status: New => Confirmed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563951 Title: