#2916 ExternalCA: Failures when installed with hsm
Closed: fixed 6 years ago Opened 6 years ago by mharmsen.

Trying to do externalCA with hsm instance and i could see some failures.

pkispawn    : INFO     ....... importing ca_signing certificate from /tmp/ca_signing.crt
pkispawn    : DEBUG    ....... Error Type: Exception
pkispawn    : DEBUG    ....... Error Message:
pkispawn    : DEBUG    .......   File "/usr/sbin/pkispawn", line 533, in main
    scriptlet.spawn(deployer)
  File "/usr/lib/python2.7/site-packages/pki/server/deployment/scriptlets/configuration.py", line 1054, in spawn
    self.import_system_certs(deployer, nssdb, subsystem)
  File "/usr/lib/python2.7/site-packages/pki/server/deployment/scriptlets/configuration.py", line 592, in import_system_certs
    self.import_ca_signing_cert(deployer, nssdb)
  File "/usr/lib/python2.7/site-packages/pki/server/deployment/scriptlets/configuration.py", line 413, in import_ca_signing_cert
    trust_attributes='CT,C,C')
  File "/usr/lib/python2.7/site-packages/pki/nssdb.py", line 762, in import_cert_chain
    self.get_cert(nickname=nickname, output_format='base64'),
  File "/usr/lib/python2.7/site-packages/pki/nssdb.py", line 669, in get_cert
    raise Exception(std_err.strip())

Steps to Reproduce:

  1. Follow 2 step procedure.Install with step1 config.
  2. change ciphers in server.xml
  3. proceed with step 2 installation

Actual results: Installation failed

Expected results: Installation should work


Metadata Update from @mharmsen:
- 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=1535797
- Custom field type adjusted to None
- Custom field version adjusted to None

6 years ago

Metadata Update from @edewata:
- Issue close_status updated to: fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5.5 (was: 10.5)

6 years ago

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

6 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:
https://github.com/dogtagpki/pki/issues/3034

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.

Metadata