action #105355
open
[desktop]Use NetworkManager as default in Tumbleweed
Added by dimstar over 2 years ago.
Updated over 1 year ago.
Category:
Bugs in existing tests
Estimated time:
(Total: 0.00 h)
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
- Subject changed from Use NetworkManager as default in Tumbleweed to [qe-core]Use NetworkManager as default in Tumbleweed
- Subject changed from [qe-core]Use NetworkManager as default in Tumbleweed to Use NetworkManager as default in Tumbleweed
- Tags set to qac
- Subject changed from Use NetworkManager as default in Tumbleweed to [desktop]Use NetworkManager as default in Tumbleweed
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.
- Category set to Bugs in existing tests
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
Also available in: Atom
PDF