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

[Chad Smith]

Agreed Alberto. I believe we've determined from cloud-init upstream that
cloud-init specifically isn't the service to set and update machine-id
on cloned golden images. It is generally up to the image creator to
unset that field and the underlying init system to ensure that is
properly configured in the case of cloned VMs.

 
That said have added an upstream commmit[1] to allow golden image creators to run: 
  sudo cloud-init clean --logs --machine-id 

This command will be available in cloud-init 22.3 and later will perform
that /etc/machine-id cleanup and is our desired best practice for folks
creating golden images in clouds.

[1] https://github.com/canonical/cloud-
init/commit/8f569d45111dce368f92883e35bfbb40bbb86091

** Changed in: cloud-init (Ubuntu)
       Status: Confirmed => Won't Fix

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