When nuxwdog is enabled pkidaemon status shows instances as stopped.
Steps to Reproduce:
1. pkicreate a CA instance. 2. # pkidaemon status Status for rhcs92-CA-example: rhcs92-CA-example is running .. [CA Status Definitions] Unsecure URL = http://example.redhat.com:8080/ca/ee/ca Secure Agent URL = https://example.redhat.com:8443/ca/agent/ca Secure EE URL = https://example.redhat.com:8443/ca/ee/ca Secure Admin URL = https://example.redhat.com:8443/ca/services PKI Console Command = pkiconsole https://example.redhat.com:8443/ca Tomcat Port = 8005 (for shutdown) [CA Configuration Definitions] PKI Instance Name: rhcs92-CA-example PKI Subsystem Type: Root CA (Security Domain) Registered PKI Security Domain Information: ========================================================================== Name: Example-rhcs92-CA URL: https://example.redhat.com:8443 ========================================================================== 3. systemctl stop pki-tomcatd@rhcs92-CA-example.service 4. If you have configured CA with HSM add the following parameter to CS.cfg. cms.tokenList=<TOKEN_NAME> 5.Move the password file from /var/lib/pki/rhcs92-CA-example/conf/password.conf another safe location. 6. # pki-server nuxwdog-enable --------------------------- Nuxwdog enabled for system. --------------------------- 7. # systemctl start pki-tomcatd-nuxwdog@rhcs92-CA-example.service [rhcs92-CA-example] Please provide the password for internal: ************ [rhcs92-CA-example] Please provide the password for hardware-<Token-Name>: ********** [rhcs92-CA-example] Please provide the password for internaldb: ********** [rhcs92-CA-example] Please provide the password for replicationdb: ********** 8. # pkidaemon status Status for rhcs92-CA-aakkiang: rhcs92-CA-example is stopped
Actual results:
pkidaemon status shows rhcs92-CA-example instance as stopped.
Expected results:
pkidaemon status should show rhcs92-CA-example instance as running with valid urls as in step #2.
Additional info:
pkidaemon may need enhancement to take into account nuxwdog instances.
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1487418 - Custom field type adjusted to None - Custom field version adjusted to None - Issue priority set to: major - Issue set to the milestone: 10.5
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Fixed via PR: https://github.com/dogtagpki/pki/pull/491
commit 08370498e120b5f2d880b4fe78cf19a488e8b8eb (HEAD -> master, origin/master, origin/HEAD) Author: Dinesh Prasanth M K <dmoluguw@redhat.com> Date: Tue Jul 21 17:39:50 2020 -0400 Fix pki-server status CLI to accept nuxwdog enabled service This patch fixes pki-server to pick up the right systemd unit file name if the nuxwdog is enabled on the PKI server. Signed-off-by: Dinesh Prasanth M K <dmoluguw@redhat.com> commit 75fed9db697d2e51137cd8cd60d8402a123b4bca Author: Dinesh Prasanth M K <dmoluguw@redhat.com> Date: Tue Jul 21 16:35:37 2020 -0400 Print the SD name when executing pki-server status Signed-off-by: Dinesh Prasanth M K <dmoluguw@redhat.com>
Metadata Update from @dmoluguw: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2926
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.