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

[pki-bot]

This issue was migrated from Pagure Issue #2413. Originally filed by rpattath (@rpattath) on 2016-07-20 22:35:32:

• Assigned to vakwetu (@vakwetu)
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=1357661

---

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"

[pki-bot]

Comment from mharmsen (@mharmsen) at 2016-07-21 23:10:14

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

[pki-bot]

Comment from vakwetu (@vakwetu) at 2016-08-02 21:49:19

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

[pki-bot]

Comment from rpattath (@rpattath) at 2017-02-27 14:09:13

Metadata Update from @rpattath:

• Issue assigned to vakwetu
• Issue set to the milestone: UNTRIAGED

[pki-bot]

Comment from mharmsen (@mharmsen) at 2017-08-31 01:09:59

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)

[pki-bot]

Comment from mharmsen (@mharmsen) at 2018-04-10 22:06:03

Per 10.5.x/10.6 Triage: FUTURE

edewata: negative case