I was attempting to install CA and KRA as separate instances and encountered the following issue.
It was very consistent.
It is possible that my kra.cfg for pkispawn isn't correct (I have not done this for a while); However, no matter what, the CA should not be brought down.
Metadata Update from @mharmsen: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1447144 - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue priority set to: critical
commit ea036b22d7d15cefb8f7a56e9c9781b545dec8ee Author: Matthew Harmsen mharmsen@redhat.com Date: Wed May 17 17:17:42 2017 -0600
Correct section headings in user deployment configuration file Bugzilla Bug #1447144 - CA brought down during separate KRA instance creation dogtagpki Pagure Issue #2674 - CA brought down during separate KRA instance creation
Metadata Update from @mharmsen: - Issue close_status updated to: fixed - Issue set to the milestone: 10.4.5 (was: 10.4) - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue assigned to mharmsen
The patch generates copies of the deployment configuration in the current folder. This creates unnecessary maintenance issue since pkispawn already stores a copy of the deployment configuration somewhere else.
Metadata Update from @edewata: - Issue status updated to: Open (was: Closed)
commit 772e05e746570c13afeb60516c07a3fb95ca3e78 Author: Endi S. Dewata edewata@redhat.com Date: Thu Jun 1 23:38:04 2017 +0200
Removed superfluous deployment configuration backup. The pkispawn has been modified to generate a temporary backup file (instead of permanent and timestamped backup files) of the deployment configuration file before normalizing its content. The temporary backup will be removed automatically when the normalization is complete. https://pagure.io/dogtagpki/issue/2674
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue set to the milestone: 10.4.7 (was: 10.4.5) - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue assigned to edewata (was: mharmsen)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.4.7-1.fc27
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/2794
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.