https://bugzilla.novell.com/show_bug.cgi?id=800365 https://bugzilla.novell.com/show_bug.cgi?id=800365#c17 --- Comment #17 from Marius Tomaschewski <mt@suse.com> 2013-02-01 10:35:26 UTC --- (In reply to comment #15)
(In reply to comment #13)
You can't continue here. The yast2 2nd stage has to run in foreground (it starts yast2 UI) and it is to finish the configuration. It (re)configures and restarts services.
OK, so the problem is cause by
a) network.service being started by default and job is waiting for YaST2 second stage to complete
yes and because systemd is trying to merge the network start with --ignore-dependencies (all the starts/restarts inside of yast2 second state) into the already queued job.
b) "systemctl restart" blocking for unit which has pending job
It seems that replacing "systemctl restart" with explicit "systemctl cancel <pending job>; systemctl start" works around this issue. "systemctl cancel" removes pending job. Which allows later to use "systemctl start --ignore-dependencies". Work for naive testing using two oneshot services.
"systemctl cancel" may work, but it would be a workaround the dependency loop. We are going to start network service before y2second-stage so there is no loop any more. See comment 5 and comment 9, Frederic already adjusted it. It just needs some time to be applied / merged by the maintainers... See also: https://github.com/yast/yast-yast2/pull/44 https://github.com/yast/yast-network/pull/47 which are needed too. -- 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.