RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Currently, the `--cert <filename>` and `--overwrite` options for `pki-server subsystem-cert-update` command hasn't been implemented. This command automates the importing of the certificate passed as argument into NSS database and overwrites the existing one.  Also, necessary changes are made in the `CS.cfg` file.

Reference: http://pki.fedoraproject.org/wiki/System_Certificate_Renewal#PKI_10.4_or_later_2

Fixed in master:
* https://github.com/dogtagpki/pki/commit/d762073c4b5bcd4f9f30e3b8439983a497a77c97

I tested this on the PKI 10.5.1-5.el7 version.

I used following steps to verify this bug:

Upgrading subsystem certificate.

1. pki -d /opt/pki/certdb/ -c Secret123 -p 20080  ca-cert-request-submit --profile caManualRenewal --serial 0x4 --renewal

2. pki -d /opt/pki/certdb/ -c Secret123 -p 20080 -n "PKI CA Administrator for Example.Org" ca-cert-request-review --action approve <request_id>

3. pki -d /opt/pki/certdb/ -c Secret123 -p 20080 cert-show <cert_id> --output subsystem_cert.crt

4. pki-server subsystem-cert-update ca subsystem -i topology-02-CA --cert subsystem_cert.crt

5. certutil -L -d /var/lib/pki/topology-02-CA/alias/ -n "subsystemCert cert-topology-02-CA" # For verification of subsystem cert is updated in the database.

Restart the instance.

If the instance is started successfully then the certificate is updated successfully.

Verifying this bug.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0925