[Bug 932605] New: Network/wicked fails to come up before second stage of Autoyast install
http://bugzilla.novell.com/show_bug.cgi?id=932605 Bug ID: 932605 Summary: Network/wicked fails to come up before second stage of Autoyast install Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening@forge.provo.novell.com Reporter: suse@aussec.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Autoyast stage 1 is started via PXE and completes as it should (including updates). After the reboot to go into Autoyast stage 2, a message comes up that wicked has failed to start. Stage 2 runs anyway and fails downloading some files as the network is obviously down. Repeatability: always This seems to be partly a dependency issue as dbus is not running but then wicked fails with the following message: wicked: /org/opensuse/Network/Interface.getManagedObjects failed. Server responds: wicked: org.freedesktop.DBus.Error.ServiceUnknown: The name org.opensuse.Network was not provided by any .service files wicked: Couldn't refresh list of active network interfaces Workaround: Go into single user mode, "systemctl start dbus". Then "systemctl restart network.service" and network comes up as desired. Then quit the single-user shell and Autoyast stage 2 completes properly. https://bugzilla.novell.com/show_bug.cgi?id=901337 has fixed a similar issue (including for 13.2, installed: yast2-packager-3.1.52.1-4.3) For reference: wicked-0.6.18-15.1, systemd-210-25.16.1 What logs are needed? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=932605 --- Comment #1 from Tom Burkart <suse@aussec.com> --- Created attachment 635924 --> http://bugzilla.novell.com/attachment.cgi?id=635924&action=edit Edited autoyast install file -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=932605 --- Comment #2 from Tom Burkart <suse@aussec.com> --- Created attachment 635925 --> http://bugzilla.novell.com/attachment.cgi?id=635925&action=edit y2start.log compressed -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=932605 --- Comment #3 from Tom Burkart <suse@aussec.com> --- Created attachment 635926 --> http://bugzilla.novell.com/attachment.cgi?id=635926&action=edit stage 2 log (edited and compressed) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=932605 --- Comment #4 from Tom Burkart <suse@aussec.com> --- Additional testing: Amended Workaround: In single-user shell, issuing "systemctl start network.service" will bring up networking and will make Autoyast stage 2 complete successfully. If a "systemctl stop network.service" is issued before leaving the shell, stage 2 will still start networking successfully and complete without problem. I have added some config and log files that I am hoping are useful but YMMV. The original server was a UEFI system but I have replicated it on a non-UEFI system. I am struggling to know what else to provide as it is rather tricky to catch things on a running system that can't be easily paused... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=932605 Pawel Wieczorkiewicz <pwieczorkiewicz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |pwieczorkiewicz@suse.com Resolution|--- |DUPLICATE --- Comment #5 from Pawel Wieczorkiewicz <pwieczorkiewicz@suse.com> --- This looks like a duplicate to boo#902464 (please see also boo#931710). *** This bug has been marked as a duplicate of bug 902464 *** -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com