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

[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 seem like the best advice would be for you to just remove the file before snapshotting an instance for re-use, so that new instances would get a new id generated.

Ideally in my mind, cloud-init or systemd or somethign would realize
that this is a new instance and do the right thing, but that seems non-
trivial at the moment. so i'll leave this as a wishlist bug on cloud-
init.

Thanks.
Scott

** Changed in: cloud-init (Ubuntu)
       Status: Invalid => Confirmed

** Changed in: cloud-init (Ubuntu)
   Importance: Medium => Wishlist

** Changed in: livecd-rootfs (Ubuntu)
       Status: Confirmed => Invalid

-- 
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