[Bug 841651] New: network@interface.service is stopped on systemctl isolate
https://bugzilla.novell.com/show_bug.cgi?id=841651 https://bugzilla.novell.com/show_bug.cgi?id=841651#c0 Summary: network@interface.service is stopped on systemctl isolate Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: arvidjaar@gmail.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- Created an attachment (id=559371) --> (http://bugzilla.novell.com/attachment.cgi?id=559371) systemd log for systemctl isolate multi-user.target User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 network@interface.service does not have any (indirect) dependency on any target so it is stopped when isolate is executed. 2013-09-21T07:25:29.626799+04:00 linux-1a7f systemd[1]: Trying to enqueue job multi-user.target/start/isolate .. 2013-09-21T07:25:29.660419+04:00 linux-1a7f systemd[1]: Installed new job network@ens3.service/stop as 347 See full log attached. On related note, stopping this service fails. For interfaces started on boot there is a workaround - generator that adds wanted by network.target; but for interfaces started manually there is no way to specify dependency. Or we need "Ignore on isolate" flag ... Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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=841651 https://bugzilla.novell.com/show_bug.cgi?id=841651#c1 --- Comment #1 from Andrey Borzenkov <arvidjaar@gmail.com> 2013-09-21 05:48:46 UTC --- Fixed with https://github.com/openSUSE/sysconfig/pull/1 (sets IgnoreOnIsolate=true) -- 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=841651 https://bugzilla.novell.com/show_bug.cgi?id=841651#c Andrey Borzenkov <arvidjaar@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED AssignedTo|bnc-team-screening@forge.pr |mt@suse.com |ovo.novell.com | -- 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=841651 https://bugzilla.novell.com/show_bug.cgi?id=841651#c2 Marius Tomaschewski <mt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |DUPLICATE --- Comment #2 from Marius Tomaschewski <mt@suse.com> 2013-09-23 09:36:55 UTC --- (In reply to comment #0) [..]
network@interface.service does not have any (indirect) dependency on any target so it is stopped when isolate is executed.
[...]
For interfaces started on boot there is a workaround - generator that adds wanted by network.target; but for interfaces started manually there is no way to specify dependency. Or we need "Ignore on isolate" flag ...
Yes, we've enabled the "Ignore on isolate" via bnc#841315. When network.service gets stopped, the "stop" is propagated to network@.service via PartOf. *** This bug has been marked as a duplicate of bug 841315 *** http://bugzilla.novell.com/show_bug.cgi?id=841315 -- 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