Project

General

Profile

action #105355

[desktop]Use NetworkManager as default in Tumbleweed

Added by dimstar 4 months ago. Updated 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Bugs in existing tests
Target version:
-
Start date:
2022-01-22
Due date:
% Done:

67%

Estimated time:
(Total: 0.00 h)
Difficulty:
Tags:

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

action #105295: [qac] setup_multimachine: migrated to Network ManagerResolvedpdostal

action #105298: [qe-core][opensuse][tumbleweed] Outdated expection in check_default_network_managerWorkable

History

#1 Updated by maritawerner 4 months ago

  • Subject changed from Use NetworkManager as default in Tumbleweed to [qe-core]Use NetworkManager as default in Tumbleweed

#2 Updated by maritawerner 4 months ago

  • Subject changed from [qe-core]Use NetworkManager as default in Tumbleweed to Use NetworkManager as default in Tumbleweed

#3 Updated by maritawerner 4 months 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 4 months 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 4 months 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 4 months ago

  • Category set to Bugs in existing tests

Also available in: Atom PDF