[Bug 811870] New: Recent commit causes SysV services not to be enabled

newer
[Bug 809972] New: x3270 fonts are...

bugzilla_noreply＠novell.com

26 Mar 2013 26 Mar '13

22:47

https://bugzilla.novell.com/show_bug.cgi?id=811870 https://bugzilla.novell.com/show_bug.cgi?id=811870#c0 Summary: Recent commit causes SysV services not to be enabled Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: joschibrauchle@gmx.de QAContact: jsrain@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/20100101 Firefox/19.0 Due to the recent commit to yast2, https://github.com/yast/yast-yast2/commit/f600967b96446de309a63ca6ed9154a4ba... Yast now calls "systemctl is-enabled <service>" to check if a service is enabled before it actually enables it. Problem: This does not work correctly for old sysvinit services due to a possible bug in systemd, see the following y2log: ---------- 2013-03-26 19:36:19 <1> student04(4489) [YCP] RunlevelEd.ycp:687 Setting nfs: ["3", "5"] 2013-03-26 19:36:19 <2> student04(4489) [YCP] Service.ycp:341 Cannot enable service nfs (just) in selected runlevels, enabling in all default ones 2013-03-26 19:36:19 <3> student04(4489) [bash] ShellCommand.cc(shellcommand):78 nfs.service is not a native service, redirecting to /sbin/chkconfig. 2013-03-26 19:36:19 <3> student04(4489) [bash] ShellCommand.cc(shellcommand):78 Executing /sbin/chkconfig nfs --level=5 ---------- The installed system ends up with nfs service not running. The reason is this: ---------- -bash-4.2# rcnfs status Checking for mounted nfs shares (from /etc/fstab):gssd not running idmapd not running unused nfs.service - LSB: NFS client services Loaded: loaded (/etc/init.d/nfs) Active: inactive (dead) CGroup: name=systemd:/system/nfs.service -bash-4.2# /sbin/chkconfig -l nfs Note: This output shows SysV services only and does not include native systemd services. SysV configuration data might be overridden by native systemd configuration. nfs 0:off 1:off 2:off 3:off 4:off 5:off 6:off -bash-4.2# systemctl is-enabled nfs.service nfs.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig nfs --level=5 nfs off enabled -bash-4.2# ---------- Clearly, "systemctl is-enabled nfs.service" incorrectly reports nfs to be "enabled" although it is disabled! Due to this wrong information and the commit mentioned above, YaST now does not enable sysvinit services because systemd tells it they would already be enabled! Reproducible: Always Steps to Reproduce: 1. Let YaST enable a sysvinit service 2. YaST calls "systemctl is-enabled <service>" which wrongly reports it to be enabled -- 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.

Show replies by date

bugzilla_noreply＠novell.com

26 Mar 26 Mar

23:00

New subject: [Bug 811870] Recent commit causes SysV services not to be enabled

https://bugzilla.novell.com/show_bug.cgi?id=811870 https://bugzilla.novell.com/show_bug.cgi?id=811870#c1 Joschi Brauchle changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |Basesystem QAContact|jsrain@suse.com |qa-bugs@suse.de --- Comment #1 from Joschi Brauchle 2013-03-26 23:00:18 UTC --- Actually, it looks like the "chkconfig" command included in aaa_base does not support the "--level" option. Also, systemctl seems to check the exit code of "chkconfig <service> --level 5", which currently does not give any indication of the service state. See: ---------- -bash-4.2# chkconfig nfs; echo $? nfs off 0 -bash-4.2# chkconfig xdm; echo $? xdm on 0 ---------- So is this a problem of chkconfig in aaa_base? -- 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.

bugzilla_noreply＠novell.com

27 Mar 27 Mar

09:31

New subject: [Bug 811870] Change in YaST causes SysVinit services not to be enabled

https://bugzilla.novell.com/show_bug.cgi?id=811870 https://bugzilla.novell.com/show_bug.cgi?id=811870#c Joschi Brauchle changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |lnussel@suse.com |ovo.novell.com | Summary|Recent commit causes SysV |Change in YaST causes |services not to be enabled |SysVinit services not to be | |enabled -- 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.

bugzilla_noreply＠novell.com

09:41

New subject: [Bug 811870] Change in YaST causes SysVinit services not to be enabled

https://bugzilla.novell.com/show_bug.cgi?id=811870 https://bugzilla.novell.com/show_bug.cgi?id=811870#c2 Joschi Brauchle changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fcrozat@suse.com --- Comment #2 from Joschi Brauchle 2013-03-27 09:41:26 UTC --- (In reply to comment #1)

...

Actually, it looks like the "chkconfig" command included in aaa_base does not support the "--level" option. Correction: It does seem to support it but does not say so in the man page.

The line where systemd decides about the status of a sysvinit service is here: http://cgit.freedesktop.org/systemd/systemd/tree/src/systemctl/systemctl.c#n... So I can't tell who's fault this is :-) -- 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.