Bug 1185262 - Unable to configure network settings with NetworkManager being active
Unable to configure network settings with NetworkManager being active
Status: CONFIRMED
Classification: openSUSE
Product: openSUSE Distribution
Classification: openSUSE
Component: YaST2
Leap 15.2
x86-64 Other
: P5 - None : Enhancement (vote)
: ---
Assigned To: YaST Team
Jiri Srain
https://trello.com/c/gSLcEyT5
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2021-04-24 19:30 UTC by Ulrich Windl
Modified: 2021-04-29 07:15 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Windl 2021-04-24 19:30:03 UTC
The default installation still using NetworkManager causes a problem in the Yast network Module:
When your try to switch to the "Overview" tab, a message pops up saying that not all settings are available, and then the tab jumps back to "Global Options".
That is you cannot even select the tab "Overview".
The other tabs ("Hostname/DNS", "Routing") are available without a popup message, however.
Comment 1 Knut Alejandro Anderssen González 2021-04-28 15:41:53 UTC
This is a change of behavior introduced by network-ng.

During installation you can decide if you want to use NetworkManager or wicked, and the default will depend on the role selected during installation.

In the past we permit to visit the Overview Tab but the config there is the wicked one, so, it was decided to show a warn and move to the overview tab where you can modify the backend in use.

In case of the other tabs, them are available because that are the allowed settings that will be modified by YaST in case that NetworkManager is used.

So, I would not consider this as a bug, although you could suggest some improvements in the workflow in order to improve the usability.
Comment 2 Ulrich Windl 2021-04-29 07:03:47 UTC
I think when a tab is not available (not accepting any input), such tab should not be there at all. I'm unsure hoe easy it is to dynamically remove a tab, or at least "gray it out".
Comment 3 Knut Alejandro Anderssen González 2021-04-29 07:14:35 UTC
(In reply to Ulrich Windl from comment #2)
> I think when a tab is not available (not accepting any input), such tab
> should not be there at all. I'm unsure hoe easy it is to dynamically remove
> a tab, or at least "gray it out".

I will add it to the incoming board as an enhancement.