action #134078
closedcoordination #151816: [epic] Handle openQA fixes and job group setup
firewall settings in yast2_rmt (and some more yast modules)
0%
Description
Observation¶
This was originally filed as
https://bugzilla.opensuse.org/show_bug.cgi?id=1207390 - YaST cannot configure the firewall when the system uses NetworkManager
The test should be adjusted to handle that limitation - in old times, there was 'stale' wicked config from install system copied to the installed system, which made 'yast believe, it can configure the firewall' - but in fact could not.
openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-yast2_ncurses@64bit fails in
yast2_rmt
Test suite description¶
Maintainer: qsf-y Test for yast2 UI, ncurses 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.
riafarov set TIMEOUT_SCALE to improve stability of the test.
Reproducible¶
Fails since (at least) Build 20221123
Expected result¶
Last good: 20180829 (or more recent)
Further details¶
Always latest result in this scenario: latest
Updated by maritawerner 9 months ago
- Project changed from openQA Tests to qe-yam
- Category deleted (
Bugs in existing tests)
Updated by openqa_review 8 months 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_ncurses
https://openqa.opensuse.org/tests/3527002#step/yast2_rmt/1
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
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Updated by openqa_review 7 months 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_ncurses
https://openqa.opensuse.org/tests/3596617#step/yast2_rmt/1
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
Expect the next reminder at the earliest in 56 days if nothing changes in this ticket.
Updated by openqa_review 6 months 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_ncurses
https://openqa.opensuse.org/tests/3738640#step/yast2_rmt/1
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
Expect the next reminder at the earliest in 112 days if nothing changes in this ticket.
Updated by openqa_review 5 months 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_ncurses
https://openqa.opensuse.org/tests/3787785#step/yast2_rmt/1
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
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Updated by JERiveraMoya 4 months ago ยท Edited
hi @zoecao what is the plan in this ticket? it seems failing since forever, could you describe the expected result?
Updated by zoecao 4 months ago
JERiveraMoya wrote in #note-8:
hi @zoecao what is the plan in this ticket? it seems failing since forever, could you describe the expected result?
I'm trying to fix it now, need to update related yast2 modules' tests to adapt the firewall interfaces not open, still updating the code:
This is the latest VR: https://openqa.opensuse.org/tests/3825121#details
Updated by zoecao 4 months ago
Already fixed the failures of yast2_rmt, yast2_tftp, yast2_vnc, yast2_ftp, VR:
- Tumbleweed: https://openqa.opensuse.org/tests/3829830#
- SLES: http://openqa.suse.de/tests/13130220# (it seems the proxySCC has some issues, will rerun it when proxySCC works fine)
There's still a failure in [dhcp_yes_eth] test module, I'm checking whether the same reason with the yast2 modules failures.
Updated by zoecao 4 months ago
PR for this ticket: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18390, welcome review, thanks.
VRs:
https://openqa.opensuse.org/tests/3846404# (tumbleweed)
https://openqa.suse.de/tests/13193568# (sles)
Updated by JERiveraMoya 4 months ago
- Tags set to qe-yam-jan-sprint
- Parent task set to #151816
Updated by openqa_review 3 months 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_ncurses
https://openqa.opensuse.org/tests/3891201#step/yast2_rmt/1
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
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.
Updated by zoecao 3 months ago
Updated PR based on comments:
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/18390
Updated by JERiveraMoya 3 months ago
- Status changed from In Progress to Resolved