Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pkiremove should be able to be run multiple times #783

Closed
pki-bot opened this issue Oct 2, 2020 · 3 comments
Closed

pkiremove should be able to be run multiple times #783

pki-bot opened this issue Oct 2, 2020 · 3 comments

Comments

@pki-bot
Copy link

pki-bot commented Oct 2, 2020

This issue was migrated from Pagure Issue #212. Originally filed by vakwetu (@vakwetu) on 2012-06-27 15:46:18:


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)

@pki-bot
Copy link
Author

pki-bot commented Oct 2, 2020

Comment from vakwetu (@vakwetu) at 2017-02-27 14:05:07

Metadata Update from @vakwetu:

  • Issue assigned to mharmsen
  • Issue set to the milestone: 9.0

@pki-bot
Copy link
Author

pki-bot commented Oct 2, 2020

Comment from edewata (@edewata) at 2019-11-04 14:35:47

This has been implemented with --force option in pkidestroy.

@pki-bot
Copy link
Author

pki-bot commented Oct 2, 2020

Comment from edewata (@edewata) at 2019-11-04 14:35:48

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant