action #125864
open[qe-core] wicked is not properly configured after switching from NM to wicked
0%
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
Updated by dimstar about 1 year ago
Wicked not being configured results in failures in dependent tests, like
https://openqa.opensuse.org/tests/3170530#
Updated by maritawerner about 1 year ago
Not sure what team should look int that, @szarate, maybe qe core?
Updated by maritawerner about 1 year 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
Updated by dimstar about 1 year ago
Updated by slo-gin 14 days ago
This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.