action #105355
[desktop]Use NetworkManager as default in Tumbleweed
100%
Description
Looking into the future, NM is becoming more important over wicked.
Tumbleweed is being prepared to use NetworkManager as the default in all scenarios - so far it only was used on graphical installations. With nmcli/nmtui, there are usable frontends for the cli as well though.
This ticket serves as a parent to a multitude of tickets exposing issues in various tests
Subtasks
History
#1
Updated by maritawerner over 1 year ago
- Subject changed from Use NetworkManager as default in Tumbleweed to [qe-core]Use NetworkManager as default in Tumbleweed
#2
Updated by maritawerner over 1 year ago
- Subject changed from [qe-core]Use NetworkManager as default in Tumbleweed to Use NetworkManager as default in Tumbleweed
#3
Updated by maritawerner over 1 year ago
Let's discuss in the QE weekly sync meeting on Wed who is in charge of NetworkManager and Network testing.
https://progress.opensuse.org/issues/105364
#4
Updated by maritawerner over 1 year ago
- Tags set to qac
- Subject changed from Use NetworkManager as default in Tumbleweed to [desktop]Use NetworkManager as default in Tumbleweed
#5
Updated by maritawerner over 1 year ago
The QE desktop team will take care of NetworkManager tests but the qac team still needs maintain the wicket tests. For more details see the related ticket.
#6
Updated by okurz over 1 year ago
- Category set to Bugs in existing tests
#7
Updated by asmorodskyi 7 months ago
- Tags deleted (
qac)
When our team was taking wicked project it was clearly defined that it does not mean that we responsible for anything related to network , wicked means ONLY wicked