buildd cloud-images used by Multipass/Snapcraft do not clear /var/lib/dbus/machine-id
Bug #1999415 reported by
Christopher Townsend
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-images |
Confirmed
|
Undecided
|
Simon Poirier | ||
launchpad-buildd |
New
|
Undecided
|
Unassigned |
Bug Description
The Multipass Team has had multiple reports over time of the same IP address being assigned the instances from the same `buildd` series. A user did some digging and reported this:
After some further investigation, the ` /var/lib/
Changed in cloud-images: | |
assignee: | nobody → Simon Poirier (simpoir) |
To post a comment you must log in.
most images using livecd-rootfs include udev, dbus, and a kernel of some sort during the bootstrap phase. Turns out, as a step during the lb_config phase, a series of cleanup actions are taken:
https:/ /git.launchpad. net/livecd- rootfs/ tree/live- build/auto/ config# n1128
add_chroot_hook update- apt-file- cache apt-xapian- index mlocate- database dbus-machine- id openssh- server- host-keys udev-persistent -rules
add_chroot_hook update-
add_chroot_hook update-
add_chroot_hook remove-
add_chroot_hook remove-
add_chroot_hook remove-
These hooks exist in upstream live-build, which Ubuntu syncs source:
https:/ /git.launchpad. net/~live- build/live- build/tree/ share/hooks/ normal
These steps are run after lb_bootstrap during lb_config, before lb_hooks. buildd is a special beast, as its seeds do not contain udev , dbus, or a kernel. buildd was originally designed to run in a container, and didn’t have requirements for those items. however, Bootable Buildd, as a virtual machine, installs them during a the build hook
https:/ /git.launchpad. net/livecd- rootfs/ tree/live- build/buildd/ hooks/52- linux-virtual- image.binary# n51
What ends up happening is the cleanup of /var/lib/ dbus/machine never occurs in buildd. and that’s a problem.
We should also check the other cleanup scripts in referenced in livecd-rootfs, pull from live-build. They may be causing other issues with the bootable buildd images.