#2290 IPA server uninstallation gives "CRITICAL" message
Closed: Invalid Opened by gkapoor.

When ipa server installed with CA chain with "BEGIN CERTIFICATE" (one
got from CA EE page), IPA server installs succeeds, but uninstall gives
"CRITICAL " message.


Unconfiguring CA
ipa.ipaserver.install.cainstance.CAInstance: CRITICAL failed to uninstall CA
instance Command /usr/sbin/pkidestroy' '-i' 'pki-tomcat' '-s' 'CA returned
non-zero exit status 1

Steps to Reproduce:

1.When external CA is tested with IPA and ca cert chain doesn't have chain
works as expected. ==> OKAY
using below steps:
a. configure ipa-server-install --external-ca.
use the csr request and generate a signed cert.  ==> Works as expected
b. /usr/sbin/ipa-server-install --external-cert-file=/root/file3
--external-cert-file=/root/file4 -vv
2. While doing ipa-server uninstall always i see : ==> NEED to check by DEV
< code snip>
ipa.ipaserver.install.cainstance.CAInstance: CRITICAL failed to uninstall CA
instance Command ''/usr/sbin/pkidestroy' '-i' 'pki-tomcat' '-s' 'CA'' returned
non-zero exit status 1
</code snip>
 ipa-server-install --uninstall -U
Shutting down all IPA services
Removing IPA client configuration
Unconfiguring ntpd
Configuring certmonger to stop tracking system certificates for KRA
Configuring certmonger to stop tracking system certificates for CA
Unconfiguring CA
ipa.ipaserver.install.cainstance.CAInstance: CRITICAL failed to uninstall CA
instance Command ''/usr/sbin/pkidestroy' '-i' 'pki-tomcat' '-s' 'CA'' returned
non-zero exit status 1
Unconfiguring web server
Unconfiguring krb5kdc
Unconfiguring kadmin
Unconfiguring directory server
Unconfiguring ipa_memcached
Unconfiguring ipa-otpd

Actual results:

Seeing "CRITICAL" message.

Expected results:

It should be clean uninstall

Additional info:

Refer https://bugzilla.redhat.com/show_bug.cgi?id=1308852 for more details.

Per CS Bug Triage held 04/19/2016: 10.3.1 or 10.3.2

Per CS/DS meeting of 04/25/2016: 10.3.1

This will take some time to setup & investigate.

I was not able to reproduce the problem with the latest code. Please feel free to reopen if it's still happening.

Metadata Update from @gkapoor:
- Issue assigned to edewata
- Issue set to the milestone: 10.3.3

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

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