https://bugzilla.novell.com/show_bug.cgi?id=800365 https://bugzilla.novell.com/show_bug.cgi?id=800365#c1 --- Comment #1 from Marius Tomaschewski 2013-01-24 18:01:19 UTC --- BTW: Workaround is to change to Console 2 and call "rcnetwork stop". This cancels the start requests and the 2nd stage yast2 starts... It seems to be needed to call it multiple times until 2nd stage finished as every "rcnetwork start" (inside of yast2) blocks. -- 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.

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.

https://bugzilla.novell.com/show_bug.cgi?id=800365 https://bugzilla.novell.com/show_bug.cgi?id=800365#c5 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsuchome@suse.com, | |lnussel@suse.com --- Comment #5 from Frederic Crozat 2013-01-28 13:49:24 UTC --- * the --ignore-dependencies deadlock has been fixed in systemd upstream this week-end and I've backported the fix, in Base:System (sr 150151) * the ordering dependency in SuSEfirewall2_init.service should be removed, to ensure only YaST2-Second-Stage.service contains dependencies against other services (easier to maintain). See attached patch * I think we should remove in YaST2-Second-Stage.service (and Firstboot) Before=network.service NetworkManager.service and uses instead : After=network.target and replacing --ignore-dependencies with --no-ask-password (the latter is needed to prevent some lockup since password agent isn't started by the time yast2 second stage is started) (see https://github.com/fcrozat/yast-installation/commit/6b317d27cbeba2c7368fda15... ) This would prevent deadlock on other services waiting for network to be up to be started. While testing this setup, I found two issues in the way YaST uses the network stack : - /etc/resolv.conf was not updated at all (calling netconfig update fixed it) - once yast2 second stage was finished, network.service was stopped otherwise, I was able to do a ssh install. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=800365 https://bugzilla.novell.com/show_bug.cgi?id=800365#c7 --- Comment #7 from Bernhard Wiedemann 2013-01-28 15:00:38 CET --- This is an autogenerated message for OBS integration: This bug (800365) was mentioned in https://build.opensuse.org/request/show/150160 Factory / systemd -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=800365 https://bugzilla.novell.com/show_bug.cgi?id=800365#c9 --- Comment #9 from Frederic Crozat 2013-01-28 14:26:07 UTC --- (In reply to comment #8)

(In reply to comment #5)

...

* I think we should remove in YaST2-Second-Stage.service (and Firstboot) ...

Frederic, please make a pull request directly for YaST2-*service files, I'm bit confused what was already implemented and what is yet to be done...

I was waiting for other people comments before doing the pull request. The only bits unknowns to me (might requires some fixes) are /etc/resolv.conf not being filled and network stack being shutdown after yast second stage is finished. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=800365 https://bugzilla.novell.com/show_bug.cgi?id=800365#c11 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arvidjaar@gmail.com --- Comment #11 from Frederic Crozat 2013-02-01 09:22:00 UTC --- *** Bug 801654 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=801654 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=800365 https://bugzilla.novell.com/show_bug.cgi?id=800365#c13 --- Comment #13 from Marius Tomaschewski 2013-02-01 09:49:43 UTC --- (In reply to comment #12)

801654 is probably due to

-> Unit network.service: Description: LSB: Configure the localfs depending network interfaces ... After: YaST2-Second-Stage.service

See comment 3, it is caused by "Before=network.service" in y2ss. "After" is adjusted by systemd automatically because of "Before".

And this service is not yet started from the systemd PoV

YaST2-Second Stage.service loaded activating start start YaST2 Second Stage

May be second stage should fork and continue to run so that service startup is "completed" from systemd PoV. Setting KillMode=none will prevent it from being "cleaned up". Otherwise you will continue to play catch game with dependencies.

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

https://bugzilla.novell.com/show_bug.cgi?id=800365 https://bugzilla.novell.com/show_bug.cgi?id=800365#c15 --- Comment #15 from Andrey Borzenkov 2013-02-01 10:21:41 UTC --- (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 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. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=800365 https://bugzilla.novell.com/show_bug.cgi?id=800365#c17 --- Comment #17 from Marius Tomaschewski 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.

https://bugzilla.novell.com/show_bug.cgi?id=800365 https://bugzilla.novell.com/show_bug.cgi?id=800365#c19 --- Comment #19 from Marius Tomaschewski 2013-02-04 09:37:11 UTC --- Yes, it makes a difference -- AFAIR yast2 does not deal (restart) with the network then as the NetworkManager is used. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=800365 https://bugzilla.novell.com/show_bug.cgi?id=800365#c21 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fehr@suse.com --- Comment #21 from Frederic Crozat 2013-02-06 08:41:50 UTC --- *** Bug 802199 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=802199 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=800365 https://bugzilla.novell.com/show_bug.cgi?id=800365#c23 Thomas Göttlicher changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpluskal@suse.com --- Comment #23 from Thomas Göttlicher 2013-02-22 17:05:08 UTC --- *** Bug 799872 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=799872 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=800365 https://bugzilla.novell.com/show_bug.cgi?id=800365#c25 --- Comment #25 from Frederic Crozat 2013-02-25 09:46:14 UTC --- so, it is too late for 12.3 to do the "clean" fixes of starting network before Second Stage, and remove --ignore-dependencies from .services. I suggest we start doing that in Factory as soon as 12.3 is out (even if 12.3 has branched from Factory, let's not loose people time on fixing Factory until it is needed). But we need to do that early in next release development cycle (before M0) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=800365 https://bugzilla.novell.com/show_bug.cgi?id=800365#c Alberto Planas Dominguez changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| | GOLD -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=800365 https://bugzilla.novell.com/show_bug.cgi?id=800365#c Martin Vidner changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks|798348 | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=800365 https://bugzilla.novell.com/show_bug.cgi?id=800365#c27 Pawel Wieczorkiewicz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED CC| |pwieczorkiewicz@suse.com Resolution| |FIXED --- Comment #27 from Pawel Wieczorkiewicz 2013-12-09 16:55:08 CET --- It is fixed (checked with the reported of this bug). -- 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.