[Bug 886512] New: After installing bind9 (named) no menue entry for service manager (YaST) to activate named at boot
https://bugzilla.novell.com/show_bug.cgi?id=886512 https://bugzilla.novell.com/show_bug.cgi?id=886512#c0 Summary: After installing bind9 (named) no menue entry for service manager (YaST) to activate named at boot Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: hfischer@eschkitai.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:30.0) Gecko/20100101 Firefox/30.0 After installing bind9/named there is no menue entry in service manager/YaST to get named starting at system boot. Trying 'systemctl enable [TAB,TAB] does not list a named.service oder a bind.service. Trying 'systemctl enable named.service' I got following message: named.service is not a native service, redirecting to /sbin/chkconfig. Executing /sbin/chkconfig named on The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). But: Now named is listed in YaST's service manager. Named can be started using the service manager. This setting remains a reboot. Looking at /etc/init.d there was listed an initscript for named. I think, starting named uses the old way over the initd way. It would be very fine, to get an service script for systemd and an entry for the service manager/YaST to enable the service. It was a lucky idea to try 'systemctl enable named.service'. But this can't be a regular solution. Reproducible: Always Steps to Reproduce: 1. Installing bind9/named with the software manager/YaST 2. Try to start/enable named for starting at boot with service manager => no named or bind 3. And now? User/admin can try /etc/init.d/named start and have to search a method for starting the named service at systemboot. (I think, an experience admin look for chkconfig, but using the systemd way is better). Expected Results: After installing bind9/named there should appear the service in the list of YaST's service manager to activate/deactivate and start/stop the service. -- 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=886512 https://bugzilla.novell.com/show_bug.cgi?id=886512#c1 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suse-beta@cboltz.de AssignedTo|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | --- Comment #1 from Christian Boltz <suse-beta@cboltz.de> 2014-07-10 00:11:23 CEST --- A likely explanation is that systemctl list-unit-files and systemctl list-units list initscripts only if they are active. Some examples: (/etc/init.d/apache2 is running, /etc/init.d/festival is not) # systemctl list-unit-files |grep apa apache2.service enabled # systemctl list-units |grep apa apache2.service loaded active running The Apache Webserver # systemctl list-units |grep festival # systemctl list-unit-files |grep festival # systemctl status festival.service festival.service - LSB: festival daemon providing full text-to-speech system Loaded: loaded (/etc/init.d/festival) Active: inactive (dead) I wouldn't be surprised if fixing list-units and list-unit-files would automagically fix the YaST service manager and the bash completion. Therefore I'm assigning this to the systemd maintainers ;-) -- 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=886512 https://bugzilla.novell.com/show_bug.cgi?id=886512#c2 Dr. Werner Fink <werner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |systemd-maintainers@suse.de Component|Network |YaST2 AssignedTo|systemd-maintainers@suse.de |yast2-maintainers@suse.de QAContact|qa-bugs@suse.de |jsrain@suse.com --- Comment #2 from Dr. Werner Fink <werner@suse.com> 2014-07-10 06:52:08 UTC --- Reading manual pages may help, e.g. man:systemctl(1) -a, --all When listing units, show all loaded units, regardless of their state, including inactive units. When showing unit/job/manager properties, show all properties regardless whether they are set or not. -- 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=886512 https://bugzilla.novell.com/show_bug.cgi?id=886512#c Michal Filka <mfilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mfilka@suse.com AssignedTo|yast2-maintainers@suse.de |locilka@suse.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=886512 https://bugzilla.novell.com/show_bug.cgi?id=886512#c3 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|locilka@suse.com |max@suse.com --- Comment #3 from Lukas Ocilka <locilka@suse.com> 2014-08-26 10:08:06 UTC --- systemd support for BIND is not a task for Yast, but for BIND itself. I have bind-9.9.5P1-1.1.x86_64 installed and I can see "named" within services operated by Services Manager. But this bug is for 13.1, so you maybe need to backport its the support. -- 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=886512 https://bugzilla.novell.com/show_bug.cgi?id=886512#c4 Reinhard Max <max@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|max@suse.com |locilka@suse.com --- Comment #4 from Reinhard Max <max@suse.com> 2014-08-26 15:26:31 CEST --- But YaST should also(In reply to comment #3)
systemd support for BIND is not a task for Yast, but for BIND itself.
AFAICS this is not about systemd support in bind, it is about missing support for SysV style init files in YaST. As (a) systemd still claims to fully support SysV style init files and (b) we can't enforce systemd support in all packages anyway, I think support for SysV style init scripts in YaST is a must. If you disagree, please close as WONTFIX, because I am not going to backport the post-13.1 systemd migration in the bind package. -- 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=886512 https://bugzilla.novell.com/show_bug.cgi?id=886512#c5 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #5 from Lukas Ocilka <locilka@suse.com> 2014-08-26 13:28:39 UTC --- It's not WONTFIX but CANTFIX, Yast can either support one or another. There's nobody who would developer and support both at the same time. -- 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=886512 https://bugzilla.novell.com/show_bug.cgi?id=886512#c6 Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | --- Comment #6 from Christian Boltz <suse-beta@cboltz.de> 2014-08-26 19:35:16 CEST --- (In reply to comment #2)
Reading manual pages may help, e.g. man:systemctl(1)
-a, --all When listing units, show all loaded units, regardless of their state, including inactive units. When showing unit/job/manager properties, show all properties regardless whether they are set or not.
@Werner: This only works with list-units. list-unit-files ignores traditional initscripts (even with -a, not sure if -a changes anything). Is this intentional or a bug? (In reply to comment #5)
It's not WONTFIX but CANTFIX, Yast can either support one or another. There's nobody who would developer and support both at the same time.
Well, using "list-units --all" instead of "list-unit-files" might already be enough. A quick grep through services_manager_service.rb indicates YaST is using both: class ServicesManagerServiceClass < Module LIST_UNIT_FILES_COMMAND = 'systemctl list-unit-files --type service' LIST_UNITS_COMMAND = 'systemctl list-units --all --type service' STATUS_COMMAND = 'systemctl status' Note: I didn't check what YaST does with the result of both commands. I know "just use list-units --all" sounds easy in theory, but I also know practise is usually more difficult ;-) -- 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=886512 https://bugzilla.novell.com/show_bug.cgi?id=886512#c7 --- Comment #7 from Dr. Werner Fink <werner@suse.com> 2014-08-26 17:55:52 UTC --- Try this for script in /etc/init.d/* ; do test -e "$script" && break test -d "$script" && continue test -x "$script" || continue systemctl status "$script.service" 2> /dev/null || continue done and then try systemctl list-units --all | grep LSB -- 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=886512 https://bugzilla.novell.com/show_bug.cgi?id=886512#c8 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEW AssignedTo|locilka@suse.com |vmoravec@suse.com --- Comment #8 from Lukas Ocilka <locilka@suse.com> 2014-08-27 08:11:14 UTC --- Implemented by Vlado, so he knows all the details, reassigning. BTW1, I believe there should be one easy way to get list of services with their properties. If it doesn't work, I'd consider that to be a bug in the base system. BTW2, named seems to be working in Yast Services Manager on my current system which is a mix of factory and SLE 12, so it seems to be working well enough, at least for me. BTW3, there should be NO hacks in Yast unless it's really necessary. -- 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