dogtagpki

#1898 pkidestroy does not remove nuxwdog service
Closed: migrated by dmoluguw. Opened by edewata.

Closed: migrated
Reopen Issue

When an instance is created it will have a systemd service: pki-tomcatd@.service.

If nuxwdog is enabled on that instance, the systemd service will change to: pki-tomcatd-nuxwdog@.service.

Normally if the instance is removed the corresponding systemd service will be removed as well. However, currently if nuxwdog is enabled, the systemd service will not be removed.

Steps to reproduce:
1. Install an instance, e.g. pki-tomcat
2. Enable nuxwdog for this instance, e.g. pki-server instance-nuxwdog-enable pki-tomcat
3. Remove the instance.

Actual result: the pki-tomcatd-nuxwdog@pki-tomcat.service link still exists in /etc/systemd/system/pki-tomcatd-nuxwdog.target.wants folder.

Expected result: the above link should be deleted.

Per CS/DS Meeting of 02/15/2016: 10.4 - minor

Metadata Update from @edewata:
- Issue set to the milestone: UNTRIAGED

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/2317

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
High
defect
Installation/Configuration
Community
minor
10.4
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.