#7446 `ipactl status` returns "named" but IPA DNS service is actually "named-pkcs11"
Closed: wontfix 2 months ago by rcritten. Opened a year ago by fbarreto.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1550197

Description of problem:
When performing `ipactl status` to look into IPA services, the DNS service is
labeled "named" instead of "named-pkcs11"


Version-Release number of selected component (if applicable):
IPA 4.5 -- ipa-server-4.5.0-21.el7.x86_64


How reproducible:
Always


Steps to Reproduce:
1. Install IPA 4.5
2. Perform `ipactl status`


Actual results:
[root@ipa74master ~]# ipactl status
Directory Service: RUNNING
krb5kdc Service: RUNNING
kadmin Service: RUNNING
named Service: RUNNING
...

Expected results:
[root@ipa74master ~]# ipactl status
Directory Service: RUNNING
krb5kdc Service: RUNNING
kadmin Service: RUNNING
named-pkcs11 Service: RUNNING
...


Additional info:
If a customer wanted to check IPA services and restart/query things manually,
having the DNS services listed as "named" is misleading and can lead to
confusion:

[root@ipa74master ~]# systemctl status named
‚óŹ named.service
   Loaded: masked (/dev/null; bad)
   Active: inactive (dead)

[root@ipa74master ~]# ps aux | grep named
named     3156  0.0  0.8 404828 33140 ?        Ssl  Feb27   0:07
/usr/sbin/named-pkcs11 -u named -c /etc/named.conf -d 3
root      4586  0.0  0.0 112664   976 pts/0    S+   13:41   0:00 grep
--color=auto named

Metadata Update from @fbarreto:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1550197

a year ago

@tjaalton The PR changes name of named to named-pkc11. It's only used for output in ipactl. Does Debian use the same names for services as Fedora / RHEL?

@amitkumar25nov The current approach doesn't work on Debian / Ubuntu.

<tjaalton> Crys: hi, it's actually bind9-pkcs11 on debian, mapped in the platform code
<tjaalton> but i think it'll be just bind-pkcs11 with 9.12

I'd rather change the names to something descriptive. Partially we are there already, we don't exactly tell systemd unit names, except for named. So I'd suggest to replace it by "DNS server" instead.

If its bind9-pkcs11, then its already showing named-pkcs11. I believe
//ipaplatform/debian/services.py
debian_system_units['named-regular'] = 'bind9.service'
debian_system_units['named-pkcs11'] = 'bind9-pkcs11.service' <<<<<<<
debian_system_units['named'] = debian_system_units['named-pkcs11']

Also what about showing descriptive name as suggested by abbra. Something as:
# ipactl status
Directory Service: RUNNING
krb5kdc Service: RUNNING
kadmin Service: RUNNING
DNS Service: STOPPED
..

The fix needs to happen within ipactl and how it reads which services are starting. However, I agree that since 'dns' has many different names across many OSes, abbra's and amitkumar25nov's suggestions are a good idea.

ipactl does not display the actual service name (as seen from systemd) in its output, as can be seen for slapd for instance:

[root@ipa74master ~]# ipactl status
Directory Service: RUNNING
krb5kdc Service: RUNNING
kadmin Service: RUNNING
named Service: RUNNING
...

but rather a label sufficient to understand which service it is referring to.
Moreover, depending on the underlying Operating System, the service name could be different.

Because of this, we decided not to modify its output. Hence closing as won't fix.

Metadata Update from @rcritten:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

2 months ago

Login to comment on this ticket.

Metadata