If something happens and pkiremove fails to run completely, we could have a situation where the instance is incompletely removed. If we try to run pkicreate to recreate the instance - this fails because of some previous artifact - whereas running pkiremove again fails because it thinks that the instance has already been removed.
In this case, the only thing that can be done is to manually do the steps in pkiremove.
Most often, I've seen that the /var/lib/foo directory (instance directory) is removed, but the registry file under /etc/sysconfig/pki remains.
We need to make this more robust for IPA (dogtag 9)
Metadata Update from @vakwetu: - Issue assigned to mharmsen - Issue set to the milestone: 9.0
This has been implemented with --force option in pkidestroy.
Metadata Update from @edewata: - 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 version adjusted to None - Issue close_status updated to: fixed - Issue set to the milestone: None (was: 9.0) - 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/783
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.