https://bugzilla.novell.com/show_bug.cgi?id=800365
https://bugzilla.novell.com/show_bug.cgi?id=800365#c3
--- Comment #3 from Frederic Crozat 2013-01-25 17:06:13 UTC ---
this entire situation is caused by :
Before=network.service
in YaST2-Second-Stage.service (and the various other dependencies) which are
forcing network and all network dependant services to be started AFTER
YaST2-Second-Stage.
Since systemd is trying to ensure all dependencies are fulfilled when starting
a service (with systemctl), systemctl calls done in YaST2-Second-Stage which
are starting a service which is waiting for network to be started (or network
itself) are being blocked until YaST2-Second-Stage is done activating (and it
won't be done, since it is "in progress", therefore the deadlock).
The "clean" fix would be to start network.service before
YaST2-Second-Service.service is started, so there wouldn't be any deadlock.
Unfortunately, doing that seems to conflict with YaST2-Second-Stage own way to
handle network installation (usessh=1 or vnc install). I'm not 100% sure of
this, this needs more testing (I'll try next week).
We should still use "--no-ask-password" for SYSTEMCTL_OPTIONS when used in
Second-Stage, since it can block systemctl calls.
--
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.