Russell Bunch

I'm working on getting debug logs, I had packer debug logs but when I tried getting vagrant debug logs my build failed on some fluke. I'm working on a rebuild...

Just had another build with unique networks defined where one of the builds never sent the DHCPREQUEST (from `sudo journalctl -xeu libvirtd -f | grep virbr`) ```bash dnsmasq-dhcp[23706]: DHCP, sockets...

@electrofelix I'll give purging the machine-id a try. This is perplexing, but perhaps related to the machine-id, but dnsmasq seems to offer the already leased IP to the new MAC....

@electrofelix in my base box I do purge the machine-id and some udev rules: ```bash #!/usr/bin/env bash set -ex echo "removing our autoyast cache to ensure no lingering sensitive content...

I tried removing `ifcfg-eth0` and saving that box, the next dual boot I did both VMs received the _same_ IP and both failed. (using the same network)  The MACs...

If it would be helpful, I can package our base box up with a different password (e.g. `vagrant`) for sharing here.

Closing this. Instead of taking our qemu sles15-base and converting it to a box with a packer post-provioner, I fixed the issue by using a vagrant builder that loads the...

@electrofelix actually, now I figured it out. I thought I had fixed the issue by using the upstream SLES-15-SP3 box made by SUSE: https://build.opensuse.org/package/show/Virtualization:Appliances:Images:SLE-15-SP3/SLES-15-SP3-Vagrant When I used that box, I...

Any updates on the outlook for this?

We are also seeing this on iLO5 BMCs as well. ```bash Set in Progress : Set Complete Auth Type Support : NONE MD5 PASSWORD Auth Type Enable : Callback :...