Description of problem:
If pki_clien_dir=/opt/rhqa_pki is specified in two subsystem's configuration files consider CA and KRA, then it CA installation will create it and stores certificates in it. Again KRA installation on same system then it delete directory and again create it.
pki_clien_dir=/opt/rhqa_pki
Result is subsystem installer does not found directory and certificate.
Error generated at the time of OCSP installation :
Error Message: [Errno 2] No such file or directory: '/opt/rhqa_pki/ca_admin.cert'
Version-Release number of selected component (if applicable): 10.3.0.b1-1.el7_2
How reproducible: Always
Steps to Reproduce: 1. Insert "pki_clien_dir=/opt/rhqa_pki" in ca.inf file and run it. 2. /opt/rhqa_pki directory will be crated and certificates are stored in this directory. 3. Insert "pki_clien_dir=/opt/rhqa_pki" in kra.inf file and run it. It remove the previously created directory and again create it. Result loss of CA certificates.
Actual results: CA installation creates it and KRA installation delete it and again create it.
Expected results: Expected that two subsystem share same directory without deletion.
https://bugzilla.redhat.com/show_bug.cgi?id=1329643
Metadata Update from @cipherboy: - Custom field component adjusted to None - 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 rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1329643 - Custom field type adjusted to None - Custom field version adjusted to None
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/3270
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.
Metadata Update from @dmoluguw: - Issue close_status updated to: migrated - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.