Project

General

Profile

action #125864

[qe-core] wicked is not properly configured after switching from NM to wicked

Added by dimstar 3 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2023-03-13
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

install system as per default install (using NetworkManager)
User installs wicked (https://openqa.opensuse.org/tests/3059152#step/switch_to_wicked/9)
User disabled NetworkManager (https://openqa.opensuse.org/tests/3059152#step/switch_to_wicked/21)
User enables (and starts) wicked (https://openqa.opensuse.org/tests/3059152#step/switch_to_wicked/23)

The configuration happened 'automatically' in the past due to a weird yast behavior where it always copied the network config used during installation, even though NetworkManager should be used; this yast bug was fixed (not leaving unrelated config)

Wicked needs to properly be configured when enabling it

openQA test in scenario opensuse-Tumbleweed-DVD-x86_64-create_hdd_gnome_wicked@64bit fails in
cleanup_before_shutdown

Test suite description

Boots into installed gnome system, switches to wicked.
Used as base job for other jobs, that require wicked to be running.

Reproducible

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

Expected result

Last good: 20230120 (or more recent)

Further details

Always latest result in this scenario: latest

History

#1 Updated by dimstar 3 months ago

Wicked not being configured results in failures in dependent tests, like
https://openqa.opensuse.org/tests/3170530#

#2 Updated by maritawerner 3 months ago

Not sure what team should look int that, szarate, maybe qe core?

#3 Updated by maritawerner 3 months ago

#4 Updated by maritawerner 2 months ago

  • Subject changed from wicked is not properly configured after switching from NM to wicked to [qe-core] wicked is not properly configured after switching from NM to wicked

Also available in: Atom PDF