action #101163
closedtest fails in yast2_lan_restart_vlan
0%
Description
The module fails because after opening yast network settings and closing without making any actual changes, it spots in logs a wicked reload that was not supposed to happen. Check if the logs are corresponding to the action or they are older logs that should not be parsed at the specific point. Check with YaST team if there are any relevant changes.
Observation¶
openQA test in scenario sle-15-SP4-Online-aarch64-yast2_gui@aarch64 fails in
yast2_lan_restart_vlan
Test suite description¶
Maintainer: zluo, riafarov
Test for yast2 UI, GUI only. Running on created gnome images which provides both text console for ncurses UI tests as well as the gnome environment for the GUI tests.
Reproducible¶
Fails since (at least) Build 36.1
Expected result¶
Last good: (unknown) (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by syrianidou_sofia over 2 years ago
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests) - Target version set to Current
Updated by oorlov over 2 years ago
- Status changed from Workable to Closed
Closed, as we have a bug ticket for this: https://bugzilla.suse.com/show_bug.cgi?id=1185775
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: yast2_gui
https://openqa.suse.de/tests/7583747
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234