QA » openQA Project » openQA Tests

It looks that the test windows_network_setup fails quite often on TW.
We need to improve the stability of windows_network_setup.

With the same windows qcow, the same test case works fine on SLE15SP4 https://openqa.suse.de/tests/7585423#next_previous
As you can see the only 2 failed test runs in history were caused by the needle mismatch and the failures were fixed by adding new needles

GraceWang wrote:

It looks that the test windows_network_setup fails quite often on TW.

'on TW' sounds misleading: Tumbleweed is not involved in booting the Windows image.

'on O3' might be more on point here then, thus a difference of O3 vs OSD?

I suspect this is related to the worker upgrade. The windows-10-x86_64-20H2@64bit_win.qcow2 image does not have network connectivity, while the one used by the WSL tests has.

The reason is that Windows saves the interface config and name indexed by the path to the device (PCI bus etc.). Using devmgmt.msc with Show hidden devices and View by connection the old adapter is visible and in a different hierarchy.

It works when using the old QEMU machine type (pc-i440fx-4.2).

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: remote-desktop-client4
https://openqa.opensuse.org/tests/2045229

To prevent further reminder comments one of the following options should be followed:

1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
3. The bugref in the openQA scenario is removed or replaced, e.g. label:wontfix:boo1234