Installation of Leap 15.1 kills Networking on Tumbleweed

English Network/Internet
#1

Tumbleweed is installed on /dev/nvme0n1p2. Added Leap on /dev/sdb5 and created a wired connection using NetworkManager. Reverted to Tumbleweed and found device configuration to fail:

Before installing Leap networking works in Tumbleweed:

    3.388825] erlangen systemd[1]: Starting Network Service...
    3.615531] erlangen systemd-networkd[750]: Enumeration completed
    3.615649] erlangen systemd[1]: Started Network Service.
    3.726319] erlangen systemd-networkd[750]: wlan0: Interface name change detected, wlan0 has been renamed to wlp3s0.
    3.786623] erlangen systemd-networkd[750]: wlp3s0: Could not bring up interface: Invalid argument
    3.827201] erlangen systemd[1]: Starting WPA Supplicant daemon (interface wlp3s0)...
    3.849303] erlangen systemd[1]: Started WPA Supplicant daemon (interface wlp3s0).
    3.926230] erlangen systemd-networkd[750]: eth0: Interface name change detected, eth0 has been renamed to enp0s31f6.
    4.879786] erlangen systemd-networkd[750]: wlp3s0: Gained carrier
    6.131150] erlangen systemd-networkd[750]: wlp3s0: Gained IPv6LL
    7.474601] erlangen systemd-networkd[750]: wlp3s0: Configured

After installing Leap and reverting to Tumbleweed networking fails:

    3.304207] erlangen systemd[1]: Starting Network Service...
    3.520386] erlangen systemd-networkd[731]: Enumeration completed
    3.520475] erlangen systemd[1]: Started Network Service.
    3.694514] erlangen systemd[1]: Starting WPA Supplicant daemon (interface wlp3s0)...
    3.714695] erlangen systemd[1]: Started WPA Supplicant daemon (interface wlp3s0).
    4.411376] erlangen systemd-networkd[731]: wlan0: Interface name change detected, wlan0 has been renamed to wlp3s0.
    4.413004] erlangen systemd[1]: wpa_supplicant@wlp3s0.service: Main process exited, code=exited, status=255/EXCEPTION
    4.413214] erlangen systemd[1]: wpa_supplicant@wlp3s0.service: Failed with result 'exit-code'.
    4.442617] erlangen systemd-networkd[731]: eth0: Interface name change detected, eth0 has been renamed to enp0s31f6.
    4.490672] erlangen systemd-networkd[731]: wlp3s0: Could not bring up interface: Invalid argument

Any idea?

#2

Pure guess… Some NetworkManager configs are local to the user. Assuming you used the same home and user directories it may be a change in config files broke Leap NM :\

#3

Network manager is not involved. Problem is caused by device renaming now taking longer and wpa supplicant starting before renaming is complete.

#4

Only thing I can think of is that your two installs aren’t as separate as you describe… Are your two installs sharing any mount points?(eg are you sharing the same /home?)
If the two installs were truly separate, booting one system would never read data from the other…

TSU

#5

Confirmed a timing problem by adding “ExecStartPre=/usr/bin/sleep 1” to unit “wpa_supplicant@.service”. Turned off device renaming by adding “net.ifnames=0” to GRUB_CMDLINE_LINUX_DEFAULT. Masked wpa* unit files and added a new unit:

erlangen:~ # cat /etc/systemd/system/wpa_supplicant-lan.service
[Unit]
Description=WPA Supplicant daemon (interface wlan0)
Before=network.target
After=dbus.service

[Service]
Type=dbus
BusName=fi.w1.wpa_supplicant1
ExecStart=/usr/sbin/wpa_supplicant -iwlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf -u -t -f /var/log/wpa_supplicant.log

[Install]
WantedBy=multi-user.target

erlangen:~ #

No more timing problems encountered.