Project

General

Profile

action #110211

JeOS also changed to NetworkManager

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

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

0%

Estimated time:
Difficulty:
Tags:
qac

Description

Observation

https://build.opensuse.org/request/show/970861 switched JeOS also to NetworkManager

openQA test in scenario opensuse-Tumbleweed-JeOS-for-kvm-and-xen-x86_64-jeos-extra@64bit_virtio-2G fails in
check_default_network_manager

Test suite description

Same as jeos, plus some more tests.

Reproducible

Fails since (at least) Build 20210824

Expected result

Last good: 20210823 (or more recent)

Further details

Always latest result in this scenario: latest

History

#1 Updated by jlausuch about 1 year ago

is this applicable only to TW?

#2 Updated by dimstar about 1 year ago

jlausuch wrote:

is this applicable only to TW?

for CODE15 this will probably remain unchanged, CODE16/ALP (whatever the name will be) is very likely to perform the switch too

#3 Updated by maritawerner about 1 year ago

  • Tags set to qac

#4 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: jeos-extra@64bit_virtio-2G
https://openqa.opensuse.org/tests/2337474#step/check_default_network_manager/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.

#6 Updated by dimstar about 1 year ago

  • Status changed from New to Resolved

Also available in: Atom PDF