Project

General

Profile

Actions

action #105295

closed

action #105355: [desktop]Use NetworkManager as default in Tumbleweed

[qac] setup_multimachine: migrated to Network Manager

Added by dimstar about 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-01-22
Due date:
% Done:

100%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-wireguard_client@64bit fails in
setup_multimachine

Tumbleweed had been changed to use Network Manager by default in all scenarios. This test falls after that switch.

Test suite description

Multimachine Wireguard client test. Maintainers: pdostal@suse.cz, pvorel@suse.cz

Reproducible

Fails since (at least) Build 20220122 (current job)

Expected result

Last good: 20220121 (or more recent)

Further details

Always latest result in this scenario: latest


Related issues 1 (0 open1 closed)

Related to openQA Tests - action #110563: remote_{ssh,vnc}-controller: failure when restarting networkResolvedpdostal2022-05-03

Actions
Actions #1

Updated by dimstar about 2 years ago

  • Parent task set to #105355
Actions #2

Updated by maritawerner about 2 years ago

@pdostal, @pvorel I am not sure which team should work on that? Could you please let me know or move it to your team?

Actions #3

Updated by okurz about 2 years ago

  • Subject changed from setup_multimachine: migrated to Network Manager to [qac] setup_multimachine: migrated to Network Manager
  • Assignee set to jlausuch

As discussed in weekly QE sync 2022-01-26 in #105364 it was decided that QAC continues to support existing wicked related testing which includes the need to adapt existing tests to explicitly install wicked before testing it.

Actions #5

Updated by jlausuch about 2 years ago

  • Assignee deleted (jlausuch)

Wait, QE-C team will take of Wicked related issues, as I'm doing for #105292 but this ticket is about some other topic (wireguard_client)...
This is out of our scope.

Actions #7

Updated by dzedro about 2 years ago

  • Status changed from New to In Progress
  • Assignee set to dzedro
Actions #8

Updated by openqa_review about 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: firewalld-policy-client
https://openqa.opensuse.org/tests/2181511

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 #9

Updated by openqa_review about 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: firewalld-policy-client
https://openqa.opensuse.org/tests/2206760

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 #11

Updated by dzedro about 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 100
Actions #13

Updated by dimstar about 2 years ago

  • Status changed from Resolved to In Progress

jlausuch wrote:

Reverted again due to some regressions https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14476

reverted implies 'no longer resolved'

Actions #15

Updated by openqa_review about 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: firewalld-policy-server
https://openqa.opensuse.org/tests/2270184#step/firewalld_policy_objects/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 #16

Updated by pdostal about 2 years ago

  • Status changed from In Progress to Resolved

Fixed.

Actions #17

Updated by openqa_review about 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: firewalld-policy-server
https://openqa.opensuse.org/tests/2303283#step/firewalld_policy_objects/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 #18

Updated by pdostal almost 2 years ago

  • Status changed from Resolved to In Progress
  • Assignee changed from dzedro to pdostal

I'm working on the problem mentioned by the bot.

Actions #19

Updated by pdostal almost 2 years ago

I'm working on pr#14746.

Actions #20

Updated by pdostal almost 2 years ago

  • Related to action #110563: remote_{ssh,vnc}-controller: failure when restarting network added
Actions #21

Updated by openqa_review almost 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: firewalld-policy-client
https://openqa.opensuse.org/tests/2327934#step/firewalld_policy_objects/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 #22

Updated by pdostal almost 2 years ago

  • Status changed from In Progress to Resolved

The setup_multimachine test module now handles both Wicked as well as Network Manager.
I created #110737 for the firewalld_policy_objects test module.

Actions #23

Updated by openqa_review almost 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_nfs_v3_server
https://openqa.opensuse.org/tests/2361693#step/yast2_nfs_server/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 #24

Updated by openqa_review almost 2 years ago

  • Status changed from Resolved to Feedback

Re-opening tickets with unhandled openqa-review reminder comment, see https://progress.opensuse.org/projects/openqatests/wiki/Wiki#openqa-review-reminder-handling

Actions #25

Updated by pdostal almost 2 years ago

  • Status changed from Feedback to In Progress
Actions #26

Updated by pdostal almost 2 years ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF