[Bug 841315] New: network breaks when changing targets
https://bugzilla.novell.com/show_bug.cgi?id=841315 https://bugzilla.novell.com/show_bug.cgi?id=841315#c0 Summary: network breaks when changing targets Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: All OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: bwiedemann@suse.com QAContact: qa-bugs@suse.de CC: dmueller@suse.com, fcrozat@suse.com Found By: Development Blocker: --- Dirk Mueller reported that init 3 broke network on Factory And I could also reproduce it with a Beta1 lxde install using systemctl isolate multi-user.target systemctl status network.service shows active (exited) both before and after the breakage and does not mention the dhcpcd process network was configured with classic ifup scripts and DHCP Reproducible: 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=841315 https://bugzilla.novell.com/show_bug.cgi?id=841315#c1 --- Comment #1 from Bernhard Wiedemann <bwiedemann@suse.com> 2013-09-19 17:32:25 CEST --- also happens when doing systemctl isolate graphical.target which should not change anything. Network comes back when using rcnetwork restart sometimes systemctl isolate graphical.target breaks ttys too which makes debugging even harder -- 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=841315 https://bugzilla.novell.com/show_bug.cgi?id=841315#c Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |mt@suse.com |ovo.novell.com | -- 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=841315 https://bugzilla.novell.com/show_bug.cgi?id=841315#c2 Bernhard Wiedemann <bwiedemann@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |mt@suse.com InfoProvider| |mt@suse.com --- Comment #2 from Bernhard Wiedemann <bwiedemann@suse.com> 2013-09-19 20:44:05 CEST --- could this be a side-effect of https://build.opensuse.org/request/show/198226 for bug 821879 ? -- 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=841315 https://bugzilla.novell.com/show_bug.cgi?id=841315#c3 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |werner@suse.com InfoProvider|mt@suse.com | --- Comment #3 from Marius Tomaschewski <mt@suse.com> 2013-09-20 08:53:51 UTC --- (In reply to comment #2)
could this be a side-effect of https://build.opensuse.org/request/show/198226 for bug 821879 ?
Yes, sure it could be [one reason why I did not commited it to 12.3 yet, but to 13.1/factory only]. But on the another side, comment #1 says, that the systemctl isolate call sometimes breaks ttys too... so IMO "everything is possible". -- 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=841315 https://bugzilla.novell.com/show_bug.cgi?id=841315#c4 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #4 from Marius Tomaschewski <mt@suse.com> 2013-09-20 08:58:53 UTC --- (In reply to comment #0)
systemctl status network.service shows active (exited) both before and after the breakage and does not mention the dhcpcd process ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is definitively a result of the bug 821879 change to use network@<ifname> service for all "ifup <ifname>" calls, that is dhcp clients are now under the cgroup of network@<ifname>.service. See also the output of the "systemctl show -p ConsistsOf network.service". -- 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=841315 https://bugzilla.novell.com/show_bug.cgi?id=841315#c5 --- Comment #5 from Bernhard Wiedemann <bwiedemann@suse.com> 2013-09-20 12:36:31 CEST --- systemctl show -p ConsistsOf network.service shows network@eth0.service and systemctl status network@eth0.service network@eth0.service - ifup managed network interface eth0 Loaded: loaded (/usr/lib/systemd/system/network@.service; static) Active: active (exited) since Thu 2013-09-19 11:35:16 EDT; 18h ago Process: 858 ExecStart=/sbin/ifup %i (code=exited, status=12) Main PID: 1001 (code=exited, status=0/SUCCESS) Sep 19 11:35:16 susetest systemd[1]: Started ifup managed network interface eth0. Sep 19 11:35:17 susetest dhcpcd[1001]: eth0: exiting Sep 19 23:35:17 susetest dhcpcd[2324]: eth0: renewing lease of 10.0.2.15 Sep 19 23:35:17 susetest dhcpcd[2324]: eth0: leased 10.0.2.15 for 86400 seconds Sep 19 23:35:17 susetest dhcpcd[2324]: eth0: no renewal time supplied, assuming 43200 seconds Sep 19 23:35:17 susetest dhcpcd[2324]: eth0: no rebind time supplied, assuming 75600 seconds Sep 19 23:35:17 susetest dhcpcd[2324]: eth0: adding IP address 10.0.2.15/24 Sep 19 23:35:17 susetest dhcpcd[2324]: eth0: adding default route via 10.0.2.2 metric 0 Sep 19 23:35:17 susetest dhcpcd[2324]: eth0: Failed to lookup hostname via DNS: Name or service not known Sep 19 23:35:17 susetest ifup[3989]: eth0 name: Ethernet Card 0 when I add an entry to /etc/hosts with the IP and long and short hostname, it works a bit better but still fails from init 5 # systemctl status network@eth0.service network@eth0.service - ifup managed network interface eth0 Loaded: loaded (/usr/lib/systemd/system/network@.service; static) Active: active (exited) since Fri 2013-09-20 06:29:36 EDT; 40s ago Process: 857 ExecStart=/sbin/ifup %i (code=exited, status=12) Main PID: 1000 (code=exited, status=0/SUCCESS) Sep 20 06:29:28 susetest ifup-dhcp[1731]: . Sep 20 06:29:30 susetest ifup-dhcp[1833]: . Sep 20 06:29:32 susetest ifup-dhcp[1935]: . Sep 20 06:29:35 susetest ifup-dhcp[2037]: . Sep 20 06:29:36 susetest ifup[857]: Starting DHCP4 client on eth0. . . . . . . Sep 20 06:29:36 susetest ifup-dhcp[2085]: Sep 20 06:29:36 susetest ifup[857]: eth0 DHCP4 continues in background Sep 20 06:29:36 susetest ifup-dhcp[2088]: eth0 DHCP4 continues in backg...d Sep 20 06:29:36 susetest systemd[1]: Started ifup managed network interface...0. Sep 20 06:29:37 susetest dhcpcd[1000]: eth0: exiting Hint: Some lines were ellipsized, use -l to show in full. but after a rcnetwork restart it looks thus: Loaded: loaded (/usr/lib/systemd/system/network@.service; static) Active: active (running) since Fri 2013-09-20 06:32:33 EDT; 3s ago Process: 3812 ExecStart=/sbin/ifup %i (code=exited, status=0/SUCCESS) Main PID: 4406 (dhcpcd) CGroup: /system.slice/system-network.slice/network@eth0.service └─4406 /sbin/dhcpcd --netconfig -L -E -HHH -c /etc/sysconfig/network/scripts/dhcpcd-hook -t 0 -h susetest eth0 Sep 20 06:32:33 susetest dhcpcd[3955]: eth0: adding default route via 10.0.2.2 metric 0 Sep 20 06:32:33 susetest ifdown[4183]: eth0 name: Ethernet Card 0 Sep 20 06:32:33 susetest dhcpcd[3955]: eth0: setting hostname to `susetest' Sep 20 06:32:33 susetest ifup[4283]: eth0 name: Ethernet Card 0 Sep 20 06:32:33 susetest dhcpcd[3955]: eth0: exiting Sep 20 06:32:33 susetest ifup[3812]: Starting DHCP4 client on eth0. Sep 20 06:32:33 susetest ifup-dhcp[4413]: Sep 20 06:32:33 susetest ifup[3812]: eth0 IP address: 10.0.2.15/24 Sep 20 06:32:33 susetest ifup-dhcp[4416]: eth0 IP address: 10.0.2.15/24 Sep 20 06:32:33 susetest systemd[1]: Started ifup managed network interface eth0. even knowing about the dhcpcd process then. still, after init 5 the status is bad: Loaded: loaded (/usr/lib/systemd/system/network@.service; static) Active: failed (Result: exit-code) since Fri 2013-09-20 06:34:12 EDT; 42s ago Process: 4535 ExecStop=/sbin/ifdown %i (code=exited, status=0/SUCCESS) Process: 3812 ExecStart=/sbin/ifup %i (code=exited, status=0/SUCCESS) Main PID: 4406 (code=exited, status=1/FAILURE) Sep 20 06:34:11 susetest ifdown[4535]: eth0 name: Ethernet Card 0 Sep 20 06:34:11 susetest ifdown[4599]: eth0 name: Ethernet Card 0 Sep 20 06:34:11 susetest dhcpcd[4629]: eth0: sending signal 15 to pid 4406 Sep 20 06:34:11 susetest dhcpcd[4406]: eth0: received SIGTERM, stopping Sep 20 06:34:11 susetest dhcpcd[4406]: eth0: removing default route via 10.0.2.2 metric 0 Sep 20 06:34:11 susetest dhcpcd[4406]: eth0: removing IP address 10.0.2.15/24 Sep 20 06:34:11 susetest dhcpcd[4406]: eth0: exiting Sep 20 06:34:11 susetest systemd[1]: network@eth0.service: main process exited, code=exited, status=1/FAILURE Sep 20 06:34:12 susetest systemd[1]: Stopped ifup managed network interface eth0. Sep 20 06:34:12 susetest systemd[1]: Unit network@eth0.service entered failed state. -- 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=841315 https://bugzilla.novell.com/show_bug.cgi?id=841315#c6 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #6 from Marius Tomaschewski <mt@suse.com> 2013-09-20 10:58:31 UTC --- This is IMO a dependency issue. A "systemctl show network.service" shows: Requires=basic.target Wants=network.target system.slice RequiredBy=network@nic0.service WantedBy=multi-user.target graphical.target ConsistsOf=network@nic0.service Conflicts=shutdown.target Before=network.target shutdown.target multi-user.target graphical.target After=YaST2-Firstboot.service YaST2-Second-Stage.service SuSEfirewall2_init.service local-fs.target earlysyslog.service isdn.service openibd.service systemd-journald.socket basic.target system.slice A "systemctl show network@nic0.service" shows: Requires=basic.target Requisite=network.service Wants=system-network.slice BindsTo=sys-subsystem-net-devices-nic0.device PartOf=network.service Conflicts=shutdown.target Before=shutdown.target After=systemd-journald.socket basic.target system-network.slice A "systemctl --all" before and after isolate shows: +accounts-daemon.service loaded active running Accounts Service network.service loaded active exited LSB: Configure network interfaces and set up routing -network@nic0.service loaded active running ifup managed network interface nic0 -xdm.service loaded inactive dead LSB: X Display Manager +xdm.service loaded active running LSB: X Display Manager -system-network.slice loaded active active system-network.slice -graphical.target loaded inactive dead Graphical Interface +graphical.target loaded active active Graphical Interface -sound.target loaded active active Sound Card +sound.target loaded inactive dead Sound Card Question is how to define correctly, that it should not be stopped? Perhaps we have to set "IgnoreOnIsolate=no" in network@.service unit? # systemctl show network@nic0.service | grep -i isolate CanIsolate=no AllowIsolate=no OnFailureIsolate=no IgnoreOnIsolate=no Werner, Frederic, any ideas? -- 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=841315 https://bugzilla.novell.com/show_bug.cgi?id=841315#c7 --- Comment #7 from Marius Tomaschewski <mt@suse.com> 2013-09-20 10:59:30 UTC --- (In reply to comment #6)
Perhaps we have to set "IgnoreOnIsolate=no" in network@.service unit?
I meant "IgnoreOnIsolate=yes" here of course... -- 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=841315 https://bugzilla.novell.com/show_bug.cgi?id=841315#c8 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|fcrozat@suse.com | --- Comment #8 from Frederic Crozat <fcrozat@suse.com> 2013-09-20 11:13:39 UTC --- (In reply to comment #7)
(In reply to comment #6)
Perhaps we have to set "IgnoreOnIsolate=no" in network@.service unit?
I meant "IgnoreOnIsolate=yes" here of course...
Yes, I think it is the solution, you want those services to survive isolate. -- 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=841315 https://bugzilla.novell.com/show_bug.cgi?id=841315#c9 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #9 from Dr. Werner Fink <werner@suse.com> 2013-09-20 11:15:18 UTC --- Hmmm ... IMHO the features of network.service should be bequeath to network@nic0.service ... maybe PartOf= or BindsTo= would be an option? -- 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=841315 https://bugzilla.novell.com/show_bug.cgi?id=841315#c10 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|fcrozat@suse.com | --- Comment #10 from Frederic Crozat <fcrozat@suse.com> 2013-09-20 11:25:22 UTC --- I've avoid BindsTo, since it would kill all services if one is failing. PartOf is nice but only for target, not for services.. And I see in network@.service : PartOf=network.service -- 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=841315 https://bugzilla.novell.com/show_bug.cgi?id=841315#c12 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |bwiedemann@suse.com --- Comment #12 from Marius Tomaschewski <mt@suse.com> 2013-09-20 14:02:49 UTC --- I've tested several times now, that IgnoreOnIsolate=yes works fine here. BTW: PartOf=network.service is already there [and propagates a stop exactly as described in the man page]. I need it to get a list of running network@ services in the init script while update/uninstall [to propagate e.g. kill to `show -p ConsistsOf network.service` to avoid network deconfiguration]. # cat /usr/lib/systemd/system/network@.service [Unit] Description=ifup managed network interface %i Requisite=network.service PartOf=network.service BindsTo=sys-subsystem-net-devices-%i.device IgnoreOnIsolate=yes [Service] Type=forking RemainAfterExit=yes ExecStart=/sbin/ifup %i ExecStop=/sbin/ifdown %i SuccessExitStatus=12 Bernhard, when it also works for you, I'd apply it monday as above. OK? -- 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=841315 https://bugzilla.novell.com/show_bug.cgi?id=841315#c13 --- Comment #13 from Bernhard Wiedemann <bwiedemann@suse.com> 2013-09-23 11:00:11 CEST --- This is an autogenerated message for OBS integration: This bug (841315) was mentioned in https://build.opensuse.org/request/show/200153 Factory / 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=841315 https://bugzilla.novell.com/show_bug.cgi?id=841315#c14 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arvidjaar@gmail.com --- Comment #14 from Marius Tomaschewski <mt@suse.com> 2013-09-23 09:36:55 UTC --- *** Bug 841651 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=841651 -- 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=841315 https://bugzilla.novell.com/show_bug.cgi?id=841315#c15 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|bwiedemann@suse.com | Resolution| |FIXED --- Comment #15 from Marius Tomaschewski <mt@suse.com> 2013-09-27 15:58:12 UTC --- Fixed & submitted. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com