Project

General

Profile

Actions
Copy link

action #134078

closed

coordination #151816: [epic] Handle openQA fixes and job group setup

firewall settings in yast2_rmt (and some more yast modules)

Added by dimstar about 1 year ago. Updated 8 months ago.

Status:
Resolved
Priority:
Low
Assignee:
zoecao
Target version:
-
Start date:
2023-08-10
Due date:
% Done:

0%

Estimated time:
Tags:
qe-yam-jan-sprint

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

Actions
Copy link
 #1

Updated by maritawerner about 1 year ago

  • Project changed from openQA Tests to qe-yam
  • Category deleted (Bugs in existing tests)
Actions
Copy link
 #2

Updated by openqa_review about 1 year 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:

  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

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions
Copy link
 #3

Updated by openqa_review about 1 year 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:

  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

Expect the next reminder at the earliest in 56 days if nothing changes in this ticket.

Actions
Copy link
 #4

Updated by openqa_review 11 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:

  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

Expect the next reminder at the earliest in 112 days if nothing changes in this ticket.

Actions
Copy link
 #5

Updated by rainerkoenig 11 months ago

  • Status changed from New to Workable
Actions
Copy link
 #6

Updated by openqa_review 10 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:

  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

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions
Copy link
 #7

Updated by zoecao 10 months ago

  • Status changed from Workable to In Progress
  • Assignee set to zoecao
Actions
Copy link
 #8

Updated by JERiveraMoya 10 months ago ยท Edited

hi @zoecao what is the plan in this ticket? it seems failing since forever, could you describe the expected result?

Actions
Copy link
 #9

Updated by JERiveraMoya 10 months ago

  • Priority changed from Normal to Low
Actions
Copy link
 #10

Updated by zoecao 10 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

Actions
Copy link
 #11

Updated by zoecao 10 months ago

Already fixed the failures of yast2_rmt, yast2_tftp, yast2_vnc, yast2_ftp, VR:

There's still a failure in [dhcp_yes_eth] test module, I'm checking whether the same reason with the yast2 modules failures.

Actions
Copy link
 #13

Updated by JERiveraMoya 9 months ago

  • Tags set to qe-yam-jan-sprint
  • Parent task set to #151816
Actions
Copy link
 #14

Updated by openqa_review 9 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:

  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

Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.

Actions
Copy link
 #16

Updated by JERiveraMoya 8 months ago

  • Status changed from In Progress to Resolved
Actions
Copy link

Also available in: Atom PDF