Bug 932605

Summary:	Network/wicked fails to come up before second stage of Autoyast install
Product:	[openSUSE] openSUSE Distribution	Reporter:	Forgotten User uoiH_jQB_V <forgotten_uoiH_jQB_V>
Component:	Network	Assignee:	wicked maintainers <wicked-maintainers>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	chcao, pwieczorkiewicz
Version:	13.2
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE 13.2
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	Edited autoyast install file y2start.log compressed stage 2 log (edited and compressed)

Description Forgotten User uoiH_jQB_V 2015-05-28 09:32:22 UTC

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?

Comment 1 Forgotten User uoiH_jQB_V 2015-05-29 05:03:00 UTC

Created attachment 635924 [details]
Edited autoyast install file

Comment 2 Forgotten User uoiH_jQB_V 2015-05-29 05:04:37 UTC

Created attachment 635925 [details]
y2start.log compressed

Comment 3 Forgotten User uoiH_jQB_V 2015-05-29 05:05:41 UTC

Created attachment 635926 [details]
stage 2 log (edited and compressed)

Comment 4 Forgotten User uoiH_jQB_V 2015-05-29 05:13:25 UTC

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...

Comment 5 Pawel Wieczorkiewicz 2015-06-01 08:59:45 UTC

This looks like a duplicate to boo#902464 (please see also boo#931710).

*** This bug has been marked as a duplicate of bug 902464 ***