Roughly during the weekend my Leap 15.1 libvirt vagrant box broke: it no longer
acquires a DHCP lease. I didn't change anything in it's configuration for the
last month and there is also nothing Leap 15.1 specific, thus I guess that this
is due to some package getting updated? (Note that the Leap 15.0 and Tumbleweed
boxes that are created from similar configs continue to work.)

I've managed to "fix" this issue by masking wickedd-dhcp6.service, which
results in the box booting again. However that isn't a proper solution.

The box takes a while to boot (without masking wickedd-dhcp6) due to it hanging
for a while at:

(1 of 3) A start job is running for wicked DHCPv6 supplicant service
(2 of 3) A start job is running for wicked AutoIPv4 supplicant service
(3 of 3) A start job is running for wicked DHCPv4 supplicant service

once it gives up, it hangs at:
A start job is running for wicked managed network service

The system log doesn't show anything pointing to the origin of the issue,
beside logging that wickedd-dhcp4/6/auto4 service failed. I've tried to sniff
the network traffic with wireshark and got no DHCP/BOOTP packages coming out of
the vagrant box.


How to reproduce:
- Install vagrant & the vagrant-libvirt plugin (via vagrant plugin install
vagrant-libvirt or from the Virtualization:vagrant repository)
- create a file called `Vagrantfile` with the following contents:

Vagrant.configure("2") do |config|
  config.vm.define "testing-15.1" do |leap_15_1|
    leap_15_1.vm.box = "openSUSE-Leap-15.1-Vagrant.x86_64"
    leap_15_1.vm.box_url =
"https://download.opensuse.org/repositories/Virtualization:/Appliances:/Images:/openSUSE-Leap-15.1/images/boxes/openSUSE-Leap-15.1-Vagrant.x86_64.json"
  end
end

- in the directory where the `Vagrantfile is, run: `vagrant up testing-15.1
--provider libvirt`

The box will fail to acquire a lease and will be stopped & deleted by vagrant
after >~10 mins. You can connect to it for via virt-manager or with
virt-viewer.