action #95845
closedIP address for accessing host network from SUT no longer automatically assigned (under Tumbleweed) size:M
Description
observation¶
The fullstack test of os-autoinst fails under Tumbleweed because eth0 (within the SUT) does not get an IP address assigned automatically anymore. Likely a change within QEMU causes this.
As a workaround the following PR has been merged: https://github.com/os-autoinst/os-autoinst/pull/1728/files
That means assigning an IP manually works and to reproduce the issue via os-autoinst's fullstack test one needs to revert 3cd3e5fe076ad4c1ee55ace70eade03d1f1f9bc8.
(Btw, the workaround should likely have assigned the IP 10.0.2.15 because 10.0.2.2 is actually the Gateway.)
The problem is not limited to the TinyCore system, it also happens with openSUSE. E.g. when cloning a test with the online_repos module (like https://openqa.opensuse.org/tests/1849850) it becomes quite apparent that the IP address is not assigned: 
(The referenced test does not fail on the production instance because on production we're using Leap which doesn't seem to be affected.)
Acceptance Criteria¶
- AC 1: Test runs again without this problem
suggestions¶
- Check for changes within Tumbleweed's QEMU package
- Check for changes of the QEMU invocation produced by os-autoinst
- Likely a DHCP problem (with the DHCP server QEMU is supposed to provide?)
- Read https://wiki.qemu.org/Documentation/Networking
- Report a bug if someone is capable to identify the regression
further notes¶
- So far I've been testing this with
qemu-6.0.0-27.1.x86_64as provided by Tumbleweed. - When just starting QEMU via
qemu-system-x86_64 -m 1024 -accel kvm -netdev user,id=qanet0 -device virtio-net,netdev=qanet0,mac=52:54:00:12:34:56than iPXE shows that the IP address is assigned correctly.
Files