Bugzilla – Bug 931710
wicked fails to start in stage2 of autoyast installation
Last modified: 2015-05-20 17:08:15 UTC
Created attachment 634909 [details] Wicked details I've been installing a fairly minimal openSUSE 13.2 system using autoyast which includes all update repositories (i.e. stage1 of installation installs all the latest RPMs for 13.2). When the system reboots into stage2, the installation process continues until it tries to access the network (e.g. when downloading post-packages). I get an error there that the network is not accessible. On vtt1 I see a red error message from systemd stating: [FAILED] Failed to start wicked managed network interfaces. Switching to vtt2, I am able to run commands as root. See attachment for all required files according to https://en.opensuse.org/openSUSE:Bugreport_wicked plus some info on all installed RPMs.
So, it looks like the missing 'org.opensuse.Network' dbus service is provided by the "wickedd.service" (notice the double-d). Starting wickedd in stage2 never returns... ------------------------- # systemctl start wickedd ------------------------- --> waits forever Doing ------------------------- # strace -fF systemctl start wickedd ------------------------- shows that is starts /run/systemd/ask-password and waits forever. By doing ------------------------- # export SYSTEMCTL_OPTIONS=--ignore-dependencies # systemctl start wickedd # systemctl start wicked ------------------------- -> succeeds So it looks like a dependency problem. Note that I've installed many (hundreds) of openSUSE 13.2 system with autoyast and wicked without problem! But all of those had a fairly large number of packages installed (>3000). They all installed fine. Thus I'm assuming some (hidden) dependency of wicked is missing in this installation!
This issue is a duplicate of boo#902464. Let's continue there. *** This bug has been marked as a duplicate of bug 902464 ***