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) Status: New => Confirmed ** Changed in: livecd-rootfs (Ubuntu) Importance: Undecided => Medium ** Changed in: cloud-init (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1563951 Title: Cloud-init does not initialize systemd machine id To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1563951/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs