[Bug 800365] New: systemd: rcnetwork start in YaST2-Second-Stage.service blocks
https://bugzilla.novell.com/show_bug.cgi?id=800365 https://bugzilla.novell.com/show_bug.cgi?id=800365#c0 Summary: systemd: rcnetwork start in YaST2-Second-Stage.service blocks Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: All URL: http://w3.suse.de/~mt/bnc798348/ OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: fcrozat@suse.com ReportedBy: mt@suse.com QAContact: jsrain@suse.com CC: locilka@suse.com, mfilka@suse.com Blocks: 798348 Found By: --- Blocker: --- This happens on factory + $OBS/home:mtomaschewski:tests/* packages also with systemd from Base:System -- most recent changelog entry: Tue Jan 22 17:02:04 UTC 2013 - fcrozat@suse.com - Add systemctl-options.patch: handle SYSTEMCTL_OPTIONS internaly (bnc#798620). ... The $OBS/home:mtomaschewski:tests/* are using network.service alias link instead of the NETWORKMANAGER=yes/no variable. While 2nd stage boot, YaST2-Second-Stage.service starts a script (and yast2-network which may restart it), which is trying to start the network. The service file is using "systemctl --ignore-dependencies" option for all services it starts/stops inside of the script via: [Unit] Before=[...]network.service[...] [Service] Type=oneshot Environment=SYSTEMCTL_OPTIONS=--ignore-dependencies TERM=linux [...] but the systemctl triggers a start of systemd-tty-ask-password-agent and it hangs then, see: http://w3.suse.de/~mt/bnc798348/network-start.console2.png Try to use "systemctl --ignore-dependencies --no-ask-password --no-block start network.service" does not help. The call returns and yast2 starts, but network is not started. It gets merged with the pending regular network.service start, see last boot in http://w3.suse.de/~mt/bnc798348/journal.txt: 2013-01-24T17:53:43.494104+01:00 linux rcnetwork[1734]: redirecting to "systemctl --ignore-dependencies --no-ask-password --no-block start network.service" 2013-01-24T17:53:43.496111+01:00 linux systemd[1]: Trying to enqueue job network.service/start/ignore-dependencies 2013-01-24T17:53:43.496113+01:00 linux systemd[1]: Merged into installed job network.service/start as 71 2013-01-24T17:53:43.496115+01:00 linux systemd[1]: Enqueued job network.service/start as 71 -- 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#c1 --- Comment #1 from Marius Tomaschewski <mt@suse.com> 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#c2 --- Comment #2 from Marius Tomaschewski <mt@suse.com> 2013-01-24 18:06:29 UTC --- As result of the above workaround, the systemd starts without network. Login + "rcnetwork start" works fine. -- 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 <fcrozat@suse.com> 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#c4 Bruno Friedmann <bruno@ioda-net.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bruno@ioda-net.ch --- Comment #4 from Bruno Friedmann <bruno@ioda-net.ch> 2013-01-26 10:04:51 UTC --- Confirmed yesterday : hit by this with remote network installation (usessh) and local. Have to rcnetwork stop at several step to be able to finish second stage. -- 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 <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsuchome@suse.com, | |lnussel@suse.com --- Comment #5 from Frederic Crozat <fcrozat@suse.com> 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#c6 --- Comment #6 from Frederic Crozat <fcrozat@suse.com> 2013-01-28 13:50:31 UTC --- Created an attachment (id=522240) --> (http://bugzilla.novell.com/attachment.cgi?id=522240) don't add dependencies about yast second stage to susefirewall -- 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 <bwiedemann@suse.com> 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#c8 --- Comment #8 from Jiří Suchomel <jsuchome@suse.com> 2013-01-28 14:14:35 UTC --- (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... -- 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 <fcrozat@suse.com> 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#c10 --- Comment #10 from Bernhard Wiedemann <bwiedemann@suse.com> 2013-01-29 10:01:39 CET --- This is an autogenerated message for OBS integration: This bug (800365) was mentioned in https://build.opensuse.org/request/show/150256 Factory / SuSEfirewall2 -- 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 <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |arvidjaar@gmail.com --- Comment #11 from Frederic Crozat <fcrozat@suse.com> 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#c12 --- Comment #12 from Andrey Borzenkov <arvidjaar@gmail.com> 2013-02-01 09:29:23 UTC --- 801654 is probably due to -> Unit network.service: Description: LSB: Configure the localfs depending network interfaces ... After: YaST2-Second-Stage.service 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. -- 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 <mt@suse.com> 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#c14 --- Comment #14 from Marius Tomaschewski <mt@suse.com> 2013-02-01 10:17:53 UTC --- Created an attachment (id=522982) --> (http://bugzilla.novell.com/attachment.cgi?id=522982) RFC: y2 2nd state scripts seems to need changes as well I don't know if the bellow is correct or not, but the existing scripts IMO aren't and needs adjustments as well. startup/Second-Stage/S07-medium makes: Y2_NETWORK_ACTIVE=0 - rcnetwork start -o onboot && Y2_NETWORK_ACTIVE=1 this should be IMO: Y2_NETWORK_ACTIVE=0 + rcnetwork status && Y2_NETWORK_ACTIVE=1 startup/Second-Stage/S09-cleanup AFAIS always stopped network before: -if test ! -z "$Y2_NETWORK_ACTIVE" ; then +if test "$Y2_NETWORK_ACTIVE" = "0" ; then rcnetwork stop -- 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 <arvidjaar@gmail.com> 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#c16 --- Comment #16 from Marius Tomaschewski <mt@suse.com> 2013-02-01 10:25:33 UTC --- The code confuses me a bit. It checked before if there are ifcfg-* files (what when NetworkManager were running?). Which sense does it make to stop network in cleanup -- just because the medium script started it? What when there were no NM running before and also no config, but the user configured & started network in yast2 2nd state? The Y2_NETWORK_ACTIVE is IMO used only in these scripts... IMO it needs a closer review by somebody who knows what yast2 is doing. -- 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 <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.
https://bugzilla.novell.com/show_bug.cgi?id=800365 https://bugzilla.novell.com/show_bug.cgi?id=800365#c18 --- Comment #18 from Andrey Borzenkov <arvidjaar@gmail.com> 2013-02-02 21:41:59 UTC --- I just performed new installation and it finished without manually intervention. I did select graphical desktop (LXDE), not minimal text install, if this makes any difference. -- 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 <mt@suse.com> 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#c20 --- Comment #20 from Bernhard Wiedemann <bwiedemann@suse.com> 2013-02-04 11:38:05 CET --- It worked now, when using Base:System as an AddOn repo (Factory is does not build images atm) and LXDE installs from Factory DVD/NET isos are affected (only Beta had the workaround in yast) -- 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 <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fehr@suse.com --- Comment #21 from Frederic Crozat <fcrozat@suse.com> 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#c22 --- Comment #22 from Andrey Borzenkov <arvidjaar@gmail.com> 2013-02-09 07:06:19 UTC --- Worked today using 12.3 RC1 NET ISO and minimal text mode installation. -- 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 <tgoettlicher@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpluskal@suse.com --- Comment #23 from Thomas Göttlicher <tgoettlicher@suse.com> 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#c24 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hendrikw@arcor.de --- Comment #24 from Jiří Suchomel <jsuchome@suse.com> 2013-02-25 09:20:31 UTC --- *** Bug 799386 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=799386 -- 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 <fcrozat@suse.com> 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 <aplanas@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |808039 -- 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 <aplanas@suse.com> 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#c26 Martin Vidner <mvidner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mvidner@suse.com --- Comment #26 from Martin Vidner <mvidner@suse.com> 2013-09-27 12:43:34 CEST --- (In reply to comment #17)
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.
The YaST pull requests were superceded by https://github.com/yast/yast-yast2/pull/51 and https://github.com/yast/yast-network/pull/61 and merged -- 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 <mvidner@suse.com> 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#c Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|fcrozat@suse.com |systemd-maintainers@suse.de -- 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 <pwieczorkiewicz@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED CC| |pwieczorkiewicz@suse.com Resolution| |FIXED --- Comment #27 from Pawel Wieczorkiewicz <pwieczorkiewicz@suse.com> 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.
participants (1)
-
bugzilla_noreply＠novell.com