dogtagpki

#263 Dogtag 10: Fix 'pkidestroy' problem of sporadically "not" removing "/etc/sysconfig/{pki_instance_id}" . . .
Closed: Fixed Opened by mharmsen.

Closed: Fixed
Reopen Issue

Occasionally, when running 'pkidestroy', the file "/etc/sysconfig/{pki_instance_id}" (which is basically the executing "tomcat.conf" for the PKI instance) does not get removed.

The code that is supposed to do this is located in the "destroy()" method of "infrastructure.py":

                  ...
                  if master['pki_subsystem'] in config.PKI_TOMCAT_SUBSYSTEMS:
                    util.file.delete(
                        master['pki_target_tomcat_conf_instance_id'])

However, I need to investigate if some of the nested logic does not get visited if the system happens to contain an additional "older" instance.

Resolved:

commit f589cc1e267d6d7b67a6463b4495b7a9c982669f
Author: Matthew Harmsen <mharmsen@redhat.com>
Date:   Sat Jul 28 18:59:30 2012 -0700

Metadata Update from @mharmsen:
- Issue assigned to mharmsen
- Issue set to the milestone: Dogtag 10.0 Alpha

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

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
None
None
None
Normal
defect
Installation/Configuration
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.