[Bug 808039] New: No network without networkmanager
https://bugzilla.novell.com/show_bug.cgi?id=808039 https://bugzilla.novell.com/show_bug.cgi?id=808039#c0 Summary: No network without networkmanager Classification: openSUSE Product: openSUSE 12.3 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: aplanas@novell.com QAContact: qa-bugs@suse.de CC: aj@suse.com, coolo@suse.com, kkaempf@suse.com, locilka@suse.com, mt@suse.com, mvidner@suse.com, ro@suse.com, paul.zirnik@suse.com, wstephenson@suse.com, f.de.kruijf@gmail.com, jarlgjessing@gmail.com, jweberhofer@weberhofer.at, bili@suse.com, rb03884@gmail.com, jpoortvliet@suse.com, fcrozat@suse.com, mfilka@suse.com Depends on: 798348,800365 Found By: --- Blocker: --- Created an attachment (id=528702) --> (http://bugzilla.novell.com/attachment.cgi?id=528702) YaST2 log after stage2 +++ This bug was initially created as a clone of Bug #798348 +++ In order to simplify the track of the bug #798348, where a partial solution where submitted, I cloned the old bug into this one. Symptoms (tested on a Lenovo x230): - After the stage2 installation process, the system has network (traditional mode). I can ping outside using a wire. - systemctl status NetworkManager.service says that the service is enabled but inactive. - YaST2 / Network Settings says that networks is controlled by NetworkManager. - After a reboot, Network Manager runs ok, and I can configure WiFi networks and Wire networks as usual. Find attached the YaST2 logs. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c1
--- Comment #1 from Li Bin
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c
Alberto Planas Dominguez
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c2
--- Comment #2 from Freek de Kruijf
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c3
Michal Filka
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c4
Marius Tomaschewski
I think, I've seen an answer for following question already somewhere in discussion, but I want to be sure, so I'm going to ask again.
Currently network starts links using "ip link set <dev> up" cmd. Is it problem for systemd? E.g. that systemd is not able to restart network properly in such case ...
I don't understand / can't follow. What do you mean exactly? Why do you think "ip link set <dev> up" cmd could break systemd? /etc/init.d/network [when in use] calls "ifup", which calls diverse "ip" commands (ip link, ip addr, ip route) which are using netlink interface to do their work and may also start other programs, e.g. dhcp client. /etc/init.d/network redirects all direct/manual calls to systemd, which calls the current network.service (that may be also NetworkManager). When /etc/init.d/network is used, systemd calls its again from PID 0 and inside of the network.service cgroup, that is all programs are started there are running inside of this cgroup. On 12.3, also all direct/manual calls to "ifup" are starting everything in the network.service cgroup. Further ifup also rejects to do anything when network.service resolves to another service, e.g. NetworkManager. The problem from comment 2 happens IMO, because in the 2nd stage makes: * /usr/lib/YaST2/startup/Second-Stage/S07-medium: Y2_NETWORK_ACTIVE=0 rcnetwork start && Y2_NETWORK_ACTIVE=1 -> when network is already started before, Y2_NETWORK_ACTIVE=1 is set! then yast2-network is started, which may stop, switch to NetworkManager (needs recent yast2, see bug 798348 comment 43 and bug 800771) and start the (new) service at the end. So basically, network is still up [when nothing fails] after yast2-network. But it gets stopped by the 2nd stage scripts: * /usr/lib/YaST2/startup/Second-Stage/S09-cleanup if test ! -z "$Y2_NETWORK_ACTIVE" ; then rcnetwork stop fi --> stop network at the end when Y2_NETWORK_ACTIVE != "" that is, it stops it always !!! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c5
Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c6
--- Comment #6 from Marius Tomaschewski
Michal,
could you please fix the 2nd stage fixes or reassign it to the proper person? ... 2nd stage scripts ...
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c7
--- Comment #7 from Michal Filka
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c8
--- Comment #8 from Michal Filka
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c9
Jiří Suchomel
But it gets stopped by the 2nd stage scripts:
* /usr/lib/YaST2/startup/Second-Stage/S09-cleanup
if test ! -z "$Y2_NETWORK_ACTIVE" ; then rcnetwork stop fi
--> stop network at the end when Y2_NETWORK_ACTIVE != "" that is, it stops it always !!!
Looks like before systemd (and even before 12.3), many services (like network) were started after YaST 2nd stage. Arvin, do you remember about this part of start up scripts? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c10
--- Comment #10 from Michal Filka
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c11
--- Comment #11 from Michal Filka
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c12
--- Comment #12 from Marius Tomaschewski
Marius: I've looked into it. It seems that the code is more than 8 years old. So, I'm curious what is the change which makes troubles. The way how is NetworkManager started?
A "systemctl --force enable NetworkManager.service" enables NM and disables ifup by creating /etc/systemd/system/network.service -> NetworkManager.service alias link and all the ./multi-user.target.wants/* links adding it to runlevels. A "disable NetworkManager.service" reverts it (removes the links). Don't forget to stop network before enabled/disable. (In reply to comment #8)
Marius: second question. rcnetwork start is called with -o onboot option. Is it ok for systemd?
Since 12.3 yes. /etc/init.d/network isn't using rc.status redirection, but makes it itself. The -o onboot is ignored [always set under systemd]. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c13
--- Comment #13 from Marius Tomaschewski
Another note:
70-persistent-net.rules
is empty on freshly installed opensuse 12.3
This IMO worth of an another bug: something for Frederic (udev maintainer). The persistent net generator has been removed, biosdevname either does not work [on my Dell OptiPlex 960, smbios 2.5] or is unreliable [Dell OptiPlex 990] and generates different names from version to version [SLE-11-SP2 & 3 at least]. When there is a rule, it is used. BTW: Persistent names are mandatory for sysconfig. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c14
Joschi Brauchle
Looks like before systemd (and even before 12.3), many services (like network) were started after YaST 2nd stage. Arvin, do you remember about this part of start up scripts?
Running a "systemctl isolate default.target" after installation starts network.service again. Such a call was added to AutoYast in bug #769924, maybe this is needed in general (not only for autoyast) after finishing stage2? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c15
--- Comment #15 from Michal Filka
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c16
--- Comment #16 from Michal Filka
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c17
Michal Filka
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c18
--- Comment #18 from Jiří Suchomel
Coolo: should be updated yast2-install package for OpenSUSE 12.3 or update it in Factory only?
If new package is installed during 2nd stage's online update step, it would replace S09-cleanup script before its execution But most users don't use interactive 2nd stage at all, so it wouldn't help them... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c19
--- Comment #19 from Joschi Brauchle
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c20
Michal Filka
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c21
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c22
Benjamin Brunner
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c23
--- Comment #23 from Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c24
--- Comment #24 from Michal Filka
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c
Michal Filka
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c25
Jiří Suchomel
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c26
Arvin Schnell
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c27
--- Comment #27 from Benjamin Brunner
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c28
--- Comment #28 from Swamp Workflow Management
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c29
Michal Filka
https://bugzilla.novell.com/show_bug.cgi?id=808039 https://bugzilla.novell.com/show_bug.cgi?id=808039#c Bug 808039 depends on bug 798348, which changed state. Bug 798348 Summary: No network without networkmanager http://bugzilla.novell.com/show_bug.cgi?id=798348 What |Old Value |New Value ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=808039 https://bugzilla.novell.com/show_bug.cgi?id=808039#c Bug 808039 depends on bug 800365, which changed state. Bug 800365 Summary: systemd: rcnetwork start in YaST2-Second-Stage.service blocks http://bugzilla.novell.com/show_bug.cgi?id=800365 What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |FIXED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c30
--- Comment #30 from Johannes Weberhofer
https://bugzilla.novell.com/show_bug.cgi?id=808039
https://bugzilla.novell.com/show_bug.cgi?id=808039#c31
Jarl Gjessing
participants (1)
-
bugzilla_noreply@novell.com