During instance creation pkispawn will generate files using the instance name in various folders. Some of these folders also contain other files, so there's a possibility of conflicts:
Changes were made to the following files to address this issue:
* pki/base/deploy/src/scriptlets/initialization.py * base/deploy/src/scriptlets/pkiconfig.py * base/deploy/src/scriptlets/pkihelper.py * base/deploy/src/scriptlets/pkimessages.py * base/deploy/src/scriptlets/pkiparser.py
RESOLVED:
commit 14243746edd14be2564b625c4a940c4723c168f1 Author: Matthew Harmsen <mharmsen@redhat.com> Date: Tue Jul 24 11:28:29 2012 -0700
PKI Deployment Scriptlets - PKI TRAC Ticket #244 - Non-user-friendly message when deleting non-existen subsystem with pkidestroy - PKI TRAC Ticket #246 - Incorrect parameter names in pkispawn configuration - PKI TRAC Ticket #248 - pki_ds_database should not be a DN - PKI TRAC Ticket #249 - pki_ds_base_dn causing pkispawn failure - PKI TRAC Ticket #250 - Creating/removing custom instances should not requi http/ajp ports - PKI TRAC Ticket #251 - Instance name may conflict with other files - PKI TRAC Ticket #253 - Fix pki-destroy removal of '/var/log/pki/{pki_instance_id}' directory . . . - PKI TRAC Ticket #254 - Dogtag 10: Fix spec file to build successfully via on Fedora 17 . . . - PKI TRAC Ticket #255 - Missing resteasy-atom-provider.jar - PKI TRAC Ticket #260 - Dogtag 10: Change the layout of 'pki_instance_id' . . .
Metadata Update from @edewata: - 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/822
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.