Bug#930645: Vagrant images debian/stretch64 9.9.1: same client ID for all VM

[Emmanuel Kasper <emmanuel@libera.cc>]

Le 17/06/2019 à 15:03, Nicolas Quiniou-Briand a écrit :
> Package: cloud.debian.org
> Severity: important
> 
> Hello,
> 
> Since upgrade to debian/stretch64 9.9.1 image, I noticed that virtual
> machines share
> the same client ID in libvirtd. Consequently, libvirtd override old DHCP
> lease by new one.
> 
thanks for the detailed bug report
I think the problems comes from every libvirt having the same
/etc/machine-id

we do delete the initial machine-id when creating the box in
https://salsa.debian.org/cloud-team/vagrant-boxes/blob/master/helpers/vagrant-setup#L103

so I suppose while working on #910143 I booted the vmdk to test the
change and the local machine-id generated at that moment ended up in all
libvirt images
IIRC this is a libvirt specific problem (again) since the virtualbox
boxes use isc-dhcp instead of the built in systemd dhcp client, and
isc-dhcp does not rely on the machine-id when requesting an IP.

as this bug is a major regression, I will move the 9.99.2 box offline
until this is fixed ( a rebuild should be enough, but I am starting my
honeymoon this week )




-- 
You know an upstream is nice when they even accept m68k patches.
  - John Paul Adrian Glaubitz, Debian OpenJDK maintainer