ipa-kra-install fails with "Error in setting certificate names and key sizes"
Steps to Reproduce:
ipa-kra-install
Actual results:
Install fails
Expected results:
Install successfully
Additional info:
The ipaserver-kra-install.log and /var/log/pki/pki-tomcat/kra/* have been attached to the associated bug. Installation failed: com.netscape.certsrv.base.PKIException: Error in setting certificate names and key sizes: java.lang.NullPointerException Please check the KRA logs in /var/log/pki/pki-tomcat/kra. 2017-05-17T19:24:36Z DEBUG stderr= 2017-05-17T19:24:36Z CRITICAL Failed to configure KRA instance: Command '/usr/sbin/pkispawn -s KRA -f /tmp/tmphynUFZ' returned non-zero exit status 1 2017-05-17T19:24:36Z DEBUG The ipa-kra-install command failed, exception: RuntimeError: KRA configuration failed. 2017-05-17T19:24:36Z ERROR KRA configuration failed.
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=1454444 - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue set to the milestone: None
Metadata Update from @mharmsen: - Issue priority set to: critical - Issue set to the milestone: 10.4
Metadata Update from @mharmsen: - Issue assigned to vakwetu
Per PKI Bug Council of 08/24/2017: 10.5
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: 10.4)
Metadata Update from @mharmsen: - Issue priority set to: major (was: critical)
[20171025] - Offline Triage ==> 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Per 10.5.x/10.6 Triage: 10.5.x
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5 (was: 10.6)
Metadata Update from @mharmsen: - Issue assigned to ftweedal (was: vakwetu)
Metadata Update from @mharmsen: - Issue close_status updated to: invalid - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue status updated to: Open (was: Closed)
Metadata Update from @mharmsen: - Issue close_status updated to: insufficient_data - Issue status updated to: Closed (was: Open)
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/2824
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.