dogtagpki

#2413 pkispawn failure due to certiifcate nickname mismatch should show proper error message
Closed: migrated by dmoluguw. Opened by rpattath.

Closed: migrated
Reopen Issue

pkispawn failure due to certiifcate nickname mismatch should show proper error
message

Steps to Reproduce:

1. Follow instructions in
http://pki.fedoraproject.org/wiki/Migrating_a_CA_using_existing_CA_mechanism
for non-hsm migration
2. pkispawn -s CA -f ca.cfg

Actual results:

Fails with the following message
[root@auto-hv-02-guest02 ~]# pkispawn -s CA -f /tmp/newca.cfg
Log file: /var/log/pki/pki-ca-spawn.20160718152024.log
Loading deployment configuration from /tmp/newca.cfg.
Installing CA into /var/lib/pki/pki-ca-July12.
Storing deployment configuration into
/etc/sysconfig/pki/tomcat/pki-ca-July12/ca/deployment.cfg.
---------------
Import complete
---------------
certutil: Could not find cert: caSigningCert cert-pki-ca-July12 CA
: PR_FILE_NOT_FOUND_ERROR: File not found
pkispawn    : ERROR    ....... pki-server subsystem-cert-validate return code:
1
pkispawn    : ERROR    .......   Cert ID: signing
  Nickname: caSigningCert cert-pki-ca-July12 CA
  Usage: SSLCA
  Token: Internal Key Storage Token
  Status: INVALID
-----------------
Validation failed
-----------------
Installation failed: Command '['pki-server', 'subsystem-cert-validate', '-i',
'pki-ca-July12', 'ca', 'signing']' returned non-zero exit status 1

Expected results:

Should fail with the error message "Cert not found"

Per PKI Bug Council of 07/21/2016: 10.3.5

Moved to 10.4. All the information is present, albeit not as nice as could be.

certutil: Could not find cert: caSigningCert cert-pki-ca-July12 CA
PR_FILE_NOT_FOUND_ERROR: File not found

Metadata Update from @rpattath:
- Issue assigned to vakwetu
- Issue set to the milestone: UNTRIAGED

Metadata Update from @mharmsen:
- Custom field feature adjusted to None
- Custom field proposedmilestone adjusted to None
- Custom field proposedpriority adjusted to None
- Custom field reviewer adjusted to None
- Custom field version adjusted to None
- Issue close_status updated to: None
- Issue priority set to: minor (was: major)
- Issue set to the milestone: FUTURE (was: UNTRIAGED)

Per 10.5.x/10.6 Triage: FUTURE

edewata: negative case

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/2533

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.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
High
None
None
None
None
None
defect
Installation/Configuration
QE
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.