http://bugzilla.suse.com/show_bug.cgi?id=1038403 http://bugzilla.suse.com/show_bug.cgi?id=1038403#c5 --- Comment #5 from Jonathan Kang <songchuan.kang@suse.com> --- (In reply to Dominique Leuenberger from comment #4)
This results in 'fun' issues as seen in https://openqa.opensuse.org/tests/1087298#step/yast2_lan/13
systemctl is-active NetworkManager claims NM is an enabled service. AS can be seen in the 'first_boot' test of this test run, NM is indeed enabled (see the nm-applet in the tray) - but YaST is not aware that networking was switched to NEtworkManager and does expect to be able to configure wicked (which is also running)
According to y2log, network.service became the alias of wicked.service instead of NetworkManager.service. So wicked thought NetworkManager is not running. Looking into it. -- You are receiving this mail because: You are on the CC list for the bug.