Bugzilla – Bug 947459
NetworkManager manages networks it shouldn't
Last modified: 2018-08-22 13:06:08 UTC
NetworkManager starts and tries to manage networks that should be managed by Wicked.
1. Install Tumbleweed build 328 from:
2. Make sure the computer is connected to a network which supports DHCP.
3. Boot the computer.
4. run yast
5. Configure for a static IP address (and set one)
6. Save and quit
6a: observe that yast restarts networking services
7. run: ip addr show
7a: Observe that the static IP address is shown, as well as an address that was pulled from DHCP.
7b: Note that ONLY the static IP should be shown
8. Reboot the computer
10. run ip addr show
10a: Observe that the busted network state (two IP addresses) persists a reboot.
11: Run yast
12: Go to network Settings
13: Hit TAB and select Global Options
14: Notice that "Network Setup Method" is Wicked (and not NetworkManager), and notice that this is the default.
15: Cancel and exit Yast
If you disable NetworkManager manually (through systemctl), this problem goes away, and the DHCP address will not show up.
To summarize the bug:
When Yast restarts network (configured with static address), the $other
network interface is configured with DHCP. This seems to be caused by
NetworkManager although only WICKED should be running. After disabling
NetworkManager manually, the problem does not appear.
Alan, could you attach Yast logs, please?
Martin, Michal, do you remember something similar from the past?
yes, there were several issues with disabling NetworkManager in the past.
Created attachment 649682 [details]
Yast logs as requested
Please disregard the yast logs attached. They won't show the issue as described, as they are for a newer release where yast doesn't work at all ( bug 947645 ). Sorry for the confusion.
I'll have to re-install Build328 to generate yast logs for you.
I have already given a very detailed process for reproducing this issue. Are you not able to reproduce it on your end?
Michal, it's not about disabling networkmanager. It should be disabled by default, at least if the yast UI is to be believed.
Added to YaST Team Scrum queue.
With the latest Tumbleweed, Build340, this problem different.
In Build340, there's no option to use NetworkManager in yast, but now the network configuration defaults to "Network Services Disabled" after a fresh install.
Yast logs attached.
Created attachment 655268 [details]
Yast Logs from Tumbleweed Build 340 aarch64. Created with save_y2logs.
Is NetworkManager installed?
I don't know whether NetworkManager is installed, and I don't have access to the hardware for the next couple of days. This new problem was observed on a fresh install of the JeOS variant of Tumbleweed, Build 340. It should be easy to determine the answer to your question on your end. What is the design of the JeOS variant?
After a fresh install, the network doesn't work. Upon looking at YaST, the network configuration indicates "Network Services Disabled". This doesn't seem appropriate for an out-of-the-box installation.
Michal, you can find out easily yourself:
grep -i manager rpm-qa
yast2-services-manager-3.1.39-2.1 (openSUSE) openSUSE Factory
grep -i network rpm-qa
yast2-network-3.1.133-1.1 (openSUSE) openSUSE Factory
(In reply to Lukas Ocilka from comment #12)
> Michal, you can find out easily yourself:
> grep -i manager rpm-qa
> yast2-services-manager-3.1.39-2.1 (openSUSE)
> openSUSE Factory
> grep -i network rpm-qa
> yast2-network-3.1.133-1.1 (openSUSE) openSUSE
it doesn't tell me if the NetworkManager is installed in reporters instance.
I currently run four virtual machines (and one physical ;-) with different products. Sadly none of them contains Tumbleweed. I'll return to this one once SLE-12-SP1 GMC deadline is over.
In general / why I asked: when NetworkManager is not installed, it is not listed in the list of services.
Consider the reporter's instance to be the default Tumbleweed Build 340 as it comes immediately after install where yast is the first command executed after the first login.
We specifically tested like that to make sure the issue was still present in 340, and it is.
Even if it isn't installed, shouldn't wicked show up as the default network configurator instead of "Network Services Disabled", so that netowrking works by default?
(In reply to Alan Ott from comment #14)
> Even if it isn't installed, shouldn't wicked show up as the default network
> configurator instead of "Network Services Disabled", so that netowrking
> works by default?
indeed it should detect wicked. I've only tried to explain why NetworkManager is not listed
According logs, the layer responsible for detecting the service reports wicked. So it seems that something strange happens in UI
To be clear, it's not just something happening in the UI of YaST, the symptom is that networking doesn't work on a fresh install. In the past it has defaulted to DHCP at least on eth0.