Your message dated Thu, 20 Feb 2020 15:07:11 +0100
with message-id <[email protected]>
and subject line Issue fixed with 9.12
has caused the Debian Bug report #930645,
regarding Vagrant images debian/stretch64 9.9.1: same client ID for all VM
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
930645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930645
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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.
### Steps to reproduce
- Create a first virtual machine:
```
mkdir stretch1/; cd stretch1; vagrant init debian/stretch64
--box-version 9.9.1
vagrant up --provider=libvirt
virsh net-dhcp-leases vagrant-libvirt
Expiry Time MAC address Protocol IP address
Hostname Client ID or DUID
-------------------------------------------------------------------------------------------------------------------
2019-06-17 15:30:00 52:54:00:fb:c7:5f ipv4 192.168.121.175/24
stretch ff:ed:10:bd:b8:00:02:00:00:ab:11:c9:17:15:e8:66:71:ae:5b
```
- Create a second virtual machine:
```
mkdir stretch2/; cd stretch2; vagrant init debian/stretch64
--box-version 9.9.1
vagrant up --provider=libvirt
virsh net-dhcp-leases vagrant-libvirt
Expiry Time MAC address Protocol IP address
Hostname Client ID or DUID
-------------------------------------------------------------------------------------------------------------------
2019-06-17 15:34:33 52:54:00:4e:d7:c6 ipv4 192.168.121.175/24
stretch ff:ed:10:bd:b8:00:02:00:00:ab:11:c9:17:15:e8:66:71:ae:5b
```
- Create a third virtual machine with previous box image:
```
mkdir stretch3/; cd stretch3; vagrant init debian/stretch64
--box-version 9.9.0
vagrant up --provider=libvirt
virsh net-dhcp-leases vagrant-libvirt
Expiry Time MAC address Protocol IP address Hostname
Client ID or DUID
-------------------------------------------------------------------------------------------------------------------
2019-06-17 15:36:14 52:54:00:3f:3a:01 ipv4 192.168.121.37/24
stretch ff:ed:10:bd:b8:00:02:00:00:ab:11:c9:80:63:ce:25:25:19:a5
2019-06-17 15:34:33 52:54:00:4e:d7:c6 ipv4 192.168.121.175/24
stretch ff:ed:10:bd:b8:00:02:00:00:ab:11:c9:17:15:e8:66:71:ae:5b
```
### Actual results
Each new machine has same client ID and same IP address as old machines.
I got exactly same client ID if I tested on different hosts.
### Expected results
Client ID should be unique, libvirtd should assign a new IP address to
new machines.
### Workaround
Spin box version to 9.9.0 in Vagrantfile:
```
config.vm.box = "debian/stretch64"
config.vm.box_version = "9.9.0"
```
### Environment
- libvirtd 4.0.0 or libvirtd 3.0.0
- vagrant-libvirt 0.0.45
- vagrant 2.2.4
- debian/stretch64 9.9.1
--
Nicolas Quiniou-Briand
[email protected] :: +1.514.447.4918 *140 :: https://inverse.ca
Inverse inc. :: Leaders behind SOGo (https://sogo.nu), PacketFence
(https://packetfence.org) and Fingerbank (http://fingerbank.org)
--
Nicolas Quiniou-Briand
Messagerie instantanée (Jabber) : [email protected]
Tél : 06 75 84 56 74
--- End Message ---
--- Begin Message ---
I am doing some bug triaging, and I noticed that the issue is fixed with
the latest stretch boxes ( 9.12)
virsh net-dhcp-leases vagrant-libvirt
Expiry Time MAC address Protocol IP address
Hostname Client ID or DUID
------------------------------------------------------------------------------------------------------------------------------------------------
2020-02-20 15:49:26 52:54:00:24:2f:9f ipv4 192.168.121.99/24
stretch ff:ed:10:bd:b8:00:02:00:00:ab:11:bc:fb:fc:f6:8b:15:c7:18
2020-02-20 16:01:16 52:54:00:89:50:38 ipv4 192.168.121.82/24
stretch ff:ed:10:bd:b8:00:02:00:00:ab:11:06:46:2c:88:f6:fe:ee:62
2020-02-20 15:55:01 52:54:00:8d:d7:24 ipv4 192.168.121.75/24
stretch ff:ed:10:bd:b8:00:02:00:00:ab:11:84:5a:61:07:cf:23:6f:d3
2020-02-20 15:53:42 52:54:00:f1:9b:41 ipv4 192.168.121.154/24
stretch ff:ed:10:bd:b8:00:02:00:00:ab:11:d3:79:62:f4:c8:fb:e6:c7
--- End Message ---
