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

[Chad Smith]

Thanks @eblock for the additional comment here. 
These behavior (to truncate /etc/machine-id on systemd) can be manually triggered by cloud-init clean --machine-id as of the following commit https://github.com/canonical/cloud-init/commit/abfdf1d83995cc20eb929d98485c321afb3a73b9

It should be in the next official release of cloud-init version 23.1 in
a couple weeks

-- 
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:
  Won't Fix
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