(systemd generates a random machine-id if there is no /etc/machine-id
whatsoever.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563951
Title:
Cloud-init does not initialize systemd machine id
To
Unfortunately, systemd reads /etc/machine-id prior to launching any
tasks, so I think this not a cloud-init issue. The proper solution, I
guess, would be to delete /etc/machine-id before making an ami out of a
running instance. Sorry to bother :(
--
You received this bug notification because you
Public bug reported:
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
Public bug reported:
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
Alexander,
please note that if a kernel process name contains "swap" as a
substring, it does not immediately mean that this process exclusively
does process memory swap-in/swap-out. kswapd is a kernel process name
for an important piece of memory management subsystem: it frees pages by
flushing
