[Bug 853908] New: No network after a fresh OpenSuSE 13.1 install
https://bugzilla.novell.com/show_bug.cgi?id=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c0 Summary: No network after a fresh OpenSuSE 13.1 install Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: i586 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: claudio.prono@atpss.net QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:6.0) Gecko/20100101 Firefox/6.0 After a problem with an upgrade test, i have decided to do a fresh test install of OpenSuSE 13.1 32bit. After configuring the network (via Yast), and doing a reboot, no network comes up at all (no ip address assigned on interface). (sorry, the date of the logs are wrong, but is only a test machine) My system is a proxmox VM guest, with this settings: linux-4tjt:~ # lspci -v | grep -i eth 00:12.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) cat /etc/sysconfig/network/ifcfg-ens18 BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='192.168.90.31/24' MTU='' NAME='RTL-8139/8139C/8139C+' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='no' systemctl status network@ens18.service -l network@ens18.service - ifup managed network interface ens18 Loaded: loaded (/usr/lib/systemd/system/network@.service; static) Active: inactive (dead) Nov 09 14:37:46 linux-4tjt systemd[1]: Starting ifup managed network interface ens18... Nov 09 14:37:47 linux-4tjt ifup[784]: ens18 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) Nov 09 14:37:47 linux-4tjt ifup[829]: ens18 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) Nov 09 14:37:48 linux-4tjt SuSEfirewall2[953]: /run/SuSEfirewall2.booting exists which means system boot in progress, exit. Nov 09 14:37:49 linux-4tjt systemd[1]: Started ifup managed network interface ens18. Nov 09 14:37:53 linux-4tjt systemd[1]: Stopping ifup managed network interface ens18... Nov 09 14:37:53 linux-4tjt ifdown[1369]: ens18 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) Nov 09 14:37:53 linux-4tjt ifdown[1410]: ens18 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) Nov 09 14:37:54 linux-4tjt systemd[1]: Stopped ifup managed network interface ens18. journalctl -u network@ens18.service -- Logs begin at Sat 2013-11-09 14:37:38 CET, end at Sat 2013-11-09 14:39:11 CET. -- Nov 09 14:37:46 linux-4tjt systemd[1]: Starting ifup managed network interface ens18... Nov 09 14:37:47 linux-4tjt ifup[784]: ens18 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) Nov 09 14:37:47 linux-4tjt ifup[829]: ens18 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) Nov 09 14:37:48 linux-4tjt SuSEfirewall2[953]: /run/SuSEfirewall2.booting exists which means system boot in progress, exit. Nov 09 14:37:49 linux-4tjt systemd[1]: Started ifup managed network interface ens18. Nov 09 14:37:53 linux-4tjt systemd[1]: Stopping ifup managed network interface ens18... Nov 09 14:37:53 linux-4tjt ifdown[1369]: ens18 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) Nov 09 14:37:53 linux-4tjt ifdown[1410]: ens18 device: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 20) Nov 09 14:37:54 linux-4tjt systemd[1]: Stopped ifup managed network interface ens18. linux-4tjt:~ # dmesg | grep ens18 [ 6.564504] systemd-udevd[245]: renamed network interface eth0 to ens18 [ 13.846605] 8139cp 0000:00:12.0 ens18: link up, 100Mbps, full-duplex, lpa 0x05E1 The same configuration, with an OpenSuSE 13.1 64bit is perfectly working. On 32bit no way to make it work. Reproducible: Always Steps to Reproduce: 1.Fresh install of OpenSuSE 13.1 (only text, no windows manager needed) 2.Configuration of the network via Yast 3.reboot 4.after reboot, no network comes up. No errors from the log. Actual Results: No working network on opensuse 13.1 32bit Expected Results: Normal network coming up after configuration and reboot -- 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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c Claudio Prono <claudio.prono@mediaservice.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P1 - Urgent -- 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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c Xiyuan Liu <xyliu@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xyliu@suse.com AssignedTo|bnc-team-screening@forge.pr |mfilka@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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c1 Simon Morris <simon@iscandar.demon.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon@iscandar.demon.co.uk --- Comment #1 from Simon Morris <simon@iscandar.demon.co.uk> 2013-12-09 16:51:39 UTC --- I've got the same effect on a 13.1 32 bit VM under Virtualbox. I can add: Networking is OK if you use network manager, only when I go to static IP & ifup control do I lose networking. -- 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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c2 --- Comment #2 from Terry Sanders <novell@vertone.co.uk> 2013-12-23 09:51:05 UTC --- Created an attachment (id=572856) --> (http://bugzilla.novell.com/attachment.cgi?id=572856) syslog for a failed netwotk on startup -- 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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c3 --- Comment #3 from Terry Sanders <novell@vertone.co.uk> 2013-12-23 09:52:22 UTC --- Created an attachment (id=572857) --> (http://bugzilla.novell.com/attachment.cgi?id=572857) sysylog for a successful network start on boot -- 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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c4 Terry Sanders <novell@vertone.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |novell@vertone.co.uk --- Comment #4 from Terry Sanders <novell@vertone.co.uk> 2013-12-23 09:54:31 UTC --- I have the same issue with a x86_64 install. This was with a minimal server installation. The networks comes up for about 6-8 seconds then goes down again. If I reboot several times then eventually the network comes up and stays up. I set the DEBUG flag to true in /etc/sysconfig/network/config and rebooted until I got logs of a failed network and a successful one. I've attached both 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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c5 Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@suse.com AssignedTo|mfilka@suse.com |mt@suse.com --- Comment #5 from Michal Filka <mfilka@suse.com> 2014-01-02 08:27:10 UTC --- @Marius: Could you look what confuses netconfig please? It seems as a kind of "systemd race condition" to me. I'm Ccing SuSEFirewall maintainer too, due to this log note: (In reply to comment #0)
Nov 09 14:37:48 linux-4tjt SuSEfirewall2[953]: /run/SuSEfirewall2.booting exists which means system boot in progress, exit. Nov 09 14:37:49 linux-4tjt systemd[1]: Started ifup managed network interface ens18. Nov 09 14:37:53 linux-4tjt systemd[1]: Stopping ifup managed network interface ens18...
-- 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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c6 --- Comment #6 from Marius Tomaschewski <mt@suse.com> 2014-01-08 13:33:22 UTC --- Please edit /usr/lib/systemd/system/network.service and change to Type=oneshot: [Service] -Type=forking +Type=oneshot Does it help? It seems that when you call "systemctl start network", which executes "systemctl start network@ens18" inside, network@ens18 service fails, because refers back via "Requisite=network.service" and network starts but is yet already started. This does not happen to me, when the network.service uses "Type=oneshot" (some RemainAfterExit=yes relation?). -- 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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c7 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |claudio.prono@mediaservice. | |net --- Comment #7 from Marius Tomaschewski <mt@suse.com> 2014-01-08 13:33:47 UTC --- See above. -- 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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c8 --- Comment #8 from Marius Tomaschewski <mt@suse.com> 2014-01-08 13:43:05 UTC --- Further, you need "systemctl daemon-reload" call after the change. Further, you may want to call "netcofig update -f" to set dns servers properly and get rid of: 2013-12-22T09:29:48.065226+00:00 pluto network[1204]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched... 2013-12-22T09:29:48.066731+00:00 pluto network[1204]: You can find my version in /etc/resolv.conf.netconfig ... -- 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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c9 --- Comment #9 from Marius Tomaschewski <mt@suse.com> 2014-01-08 14:55:18 UTC --- Test package is in: http://download.opensuse.org/repositories/home:/mtomaschewski:/branches:/ope... -- 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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c10 Claudio Prono <claudio.prono@mediaservice.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|claudio.prono@mediaservice. | |net | --- Comment #10 from Claudio Prono <claudio.prono@mediaservice.net> 2014-01-08 16:03:15 UTC --- (In reply to comment #6)
Please edit /usr/lib/systemd/system/network.service and change to Type=oneshot:
[Service] -Type=forking +Type=oneshot
Does it help?
It seems that when you call "systemctl start network", which executes "systemctl start network@ens18" inside, network@ens18 service fails, because refers back via "Requisite=network.service" and network starts but is yet already started. This does not happen to me, when the network.service uses "Type=oneshot" (some RemainAfterExit=yes relation?).
Gotcha! Changing the Type to oneshot, the problem is gone away... Now i test the test package. Thanks, Claudio. -- 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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c11 --- Comment #11 from Claudio Prono <claudio.prono@mediaservice.net> 2014-01-08 16:35:26 UTC --- (In reply to comment #9)
Test package is in:
http://download.opensuse.org/repositories/home:/mtomaschewski:/branches:/ope...
I confirm also the test package works correctly. -- 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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c12 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |maintenance@opensuse.org --- Comment #12 from Marius Tomaschewski <mt@suse.com> 2014-01-09 12:31:15 UTC --- OK, great -- thanks for verification! Maintenance, I've created request id #213291 -> openSUSE:13.1:Update - rcnetwork: use service type oneshot, not forking Sometimes, network fails to start / stops itself, because the per interface services started inside it, need already started network and fail as network did not yet reached started state. This does not happen with oneshot network service type (bnc#853908). [+ 0008-rcnetwork-use-service-type-oneshot-not-forking.patch] 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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c13 --- Comment #13 from Bernhard Wiedemann <bwiedemann@suse.com> 2014-01-09 14:00:11 CET --- This is an autogenerated message for OBS integration: This bug (853908) was mentioned in https://build.opensuse.org/request/show/213291 13.1 / 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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c14 Marcus Meissner <meissner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|maintenance@opensuse.org | --- Comment #14 from Marcus Meissner <meissner@suse.com> 2014-01-09 13:47:17 UTC --- accepted -- 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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c15 --- Comment #15 from Bernhard Wiedemann <bwiedemann@suse.com> 2014-01-09 16:00:14 CET --- This is an autogenerated message for OBS integration: This bug (853908) was mentioned in https://build.opensuse.org/request/show/213298 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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c16 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #16 from Marius Tomaschewski <mt@suse.com> 2014-01-09 15:40:09 UTC --- OK, fixed & updated accepted. -- 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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c17 --- Comment #17 from Bernhard Wiedemann <bwiedemann@suse.com> 2014-01-13 18:00:23 CET --- This is an autogenerated message for OBS integration: This bug (853908) was mentioned in https://build.opensuse.org/request/show/213765 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=853908 https://bugzilla.novell.com/show_bug.cgi?id=853908#c18 --- Comment #18 from Swamp Workflow Management <swamp@suse.de> 2014-01-16 10:05:59 UTC --- openSUSE-RU-2014:0080-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 853908 CVE References: Sources used: openSUSE 13.1 (src): sysconfig-0.81.5-10.1 -- 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