FreeIPA's CI ran into an issue with pkispawn. An incomplete installation of Dogtag has left some files and directories around. This is also a common situation during development, too. pkidestroy should have a --force option that forcefully removes all remnants of a previous installation. With --force pkidestroy should first attempt to do a regular de-installation.
Endi's pki-nuke.sh script has a list of all directories that should be removed:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23
#!/bin/sh INSTANCE_NAME=$1 if [ "$INSTANCE_NAME" == "" ]; then echo "usage: pki-nuke.sh <instance name>" exit 1 fi echo "Deleting instance $INSTANCE_NAME" pids="`ps -ef | grep catalina.base=/var/lib/pki/$INSTANCE_NAME | grep -v grep | awk '{print $2}'`" for pid in $pids; do kill -9 $pid done rm -rf /etc/pki/$INSTANCE_NAME rm -rf /etc/sysconfig/$INSTANCE_NAME rm -rf /etc/sysconfig/pki/tomcat/$INSTANCE_NAME rm -rf /var/lib/pki/$INSTANCE_NAME rm -rf /var/log/pki/$INSTANCE_NAME rm -rf /var/log/pki/pki-*.log rm -rf $HOME/.dogtag/$INSTANCE_NAME
Please don't remove logfiles if possible :)
Per CS/DS Meeting of 08/08/2016: 10.3.6
NOTE: As this ticket is probably not major, we decided to move it to 10.3.6. If we can get a 'Dogtag 10.3.6: Miscellaneous Enhancements' bug accepted with an exception flag, this bug would be a candidate for that. Otherwise, this bug will be moved to 10.4.
Per PKI Bug Council of 08/31/2016: 10.4
Per PKI Bug Council of 11/29/2016: 10.4 - critical
This is actually a duplicate of ticket #1172.
Metadata Update from @cheimes: - Issue set to the milestone: 10.4
Metadata Update from @mharmsen: - Custom field feature adjusted to '' - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field version adjusted to '' - Issue close_status updated to: None (was: Duplicate) - Issue set to the milestone: 10.4.0 (was: 10.4)
Metadata Update from @mharmsen: - Issue close_status updated to: duplicate
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/2546
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.