Cloning failed due to pki pkcs12-cert-find failure: https://bodhi.fedoraproject.org/updates/FEDORA-2017-9c6007b406
2017-03-17 09:33:07 pkispawn : DEBUG ....... Error Message: Command '['pki', '-d', '/etc/pki/pki-tomcat/alias', '-C', '/etc/pki/pki-tomcat/pfile', 'pkcs12-cert-find', '--pkcs12-file', '/tmp/ca.p12', '--pkcs12-password-file', '/tmp/tmprEFMD1/password.txt']' returned non-zero exit status 255 2017-03-17 09:33:07 pkispawn : DEBUG ....... File "/usr/sbin/pkispawn", line 500, in main scriptlet.spawn(deployer) File "/usr/lib/python2.7/site-packages/pki/server/deployment/scriptlets/security_databases.py", line 146, in spawn pkcs12.show_certs() File "/usr/lib/python2.7/site-packages/pki/pkcs12.py", line 73, in show_certs subprocess.check_call(cmd) File "/usr/lib64/python2.7/subprocess.py", line 186, in check_call raise CalledProcessError(retcode, cmd)
Metadata Update from @edewata: - Issue assigned to edewata
Fixed in master: * 6bcb89b55db870766ddcf09002a5997b323bd196
Metadata Update from @edewata: - 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 type adjusted to defect - Custom field version adjusted to '' - Issue close_status updated to: fixed - Issue set to the milestone: 10.4 - Issue status updated to: Closed (was: Open)
Metadata Update from @edewata: - Issue priority set to: 1
Metadata Update from @mharmsen: - Issue set to the milestone: 10.4.1 (was: 10.4)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to pki-core-10.4.1-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/2732
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.