#2612 Unable to clone due to pki pkcs12-cert-find failure
Closed: fixed 5 years ago Opened 5 years ago by edewata.

Cloning failed due to pki pkcs12-cert-find failure:

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
  File "/usr/lib/python2.7/site-packages/pki/server/deployment/scriptlets/security_databases.py", line 146, in spawn
  File "/usr/lib/python2.7/site-packages/pki/pkcs12.py", line 73, in show_certs
  File "/usr/lib64/python2.7/subprocess.py", line 186, in check_call
    raise CalledProcessError(retcode, cmd)

Metadata Update from @edewata:
- Issue assigned to edewata

5 years ago

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)

5 years ago

Metadata Update from @edewata:
- Issue priority set to: 1

5 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.4.1 (was: 10.4)

5 years ago

Metadata Update from @mharmsen:
- Custom field fixedinversion adjusted to pki-core-10.4.1-1.fc27

5 years ago

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:

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Login to comment on this ticket.