Project

General

Profile

Actions
Copy link

action #101620

closed

[desktop] test fails in windows_network_setup

Added by dimstar over 2 years ago. Updated over 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
favogt
Category:
Bugs in existing tests
Target version:
-
Start date:
2021-10-28
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-remote-desktop-client4@64bit fails in
windows_network_setup

Test seems failing quite often

Test suite description

The base test suite is used for job templates defined in YAML documents. It has no settings of its own.

Reproducible

Fails since (at least) Build 20211026

Expected result

Last good: 20211025 (or more recent)

Further details

Always latest result in this scenario: latest

Related issues 1 (0 open — 1 closed)

Related to openQA Tests - action #104071: [desktop] [15SP4] test fails in windows_network_setupResolvedGraceWang2021-12-16

Actions
Actions
Copy link
 #1

Updated by maritawerner over 2 years ago

  • Subject changed from test fails in windows_network_setup to [desktop] test fails in windows_network_setup
Actions
Copy link
 #2

Updated by GraceWang over 2 years ago

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

Actions
Copy link
 #3

Updated by dimstar over 2 years ago

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?

Actions
Copy link
 #4

Updated by favogt over 2 years ago

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.

Actions
Copy link
 #5

Updated by favogt over 2 years ago

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).

Actions
Copy link
 #6

Updated by favogt over 2 years ago

  • Status changed from New to Resolved
  • Assignee set to favogt

I set QEMUMACHINE=pc-i440fx-4.2 for those tests and cloned the failing jobs in TW 20211102, seems to work:

https://openqa.opensuse.org/tests/2013630
https://openqa.opensuse.org/tests/2013638
https://openqa.opensuse.org/tests/2013640

(openqa-clone-job --within-instance https://openqa.opensuse.org --skip-chained-deps --parental-inheritance 2010490 QEMUMACHINE=pc-i440fx-4.2)

Actions
Copy link
 #7

Updated by openqa_review over 2 years ago

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
Actions
Copy link
 #8

Updated by GraceWang over 2 years ago

  • Related to action #104071: [desktop] [15SP4] test fails in windows_network_setup added
Actions
Copy link

Also available in: Atom PDF