[Bug 1563951] Re: Cloud-init does not initialize systemd machine id
Oliver Grawert
ogra at ubuntu.com
Wed Apr 13 11:37:01 UTC 2016
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
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1563951
Title:
Cloud-init does not initialize systemd machine id
Status in cloud-init package in Ubuntu:
Confirmed
Status in livecd-rootfs package in Ubuntu:
Invalid
Bug description:
Systemd uses /etc/machine-id file to uniquely identify the machine and
to provide machine ID to D-Bus. This file is generated with `systemd-
machine-id-setup` command that should be run on system installation
(or at least when a system is provisioned). However, cloud-init does
not do this.
As far as I can see, all Wily Werewolf VMs provisioned in EC2 have the
same machine-id ff1bed6402c14c57ac03a074cdb7479e.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1563951/+subscriptions
More information about the foundations-bugs
mailing list