dogtagpki

#2419 Provide In-Place Upgrade Procedure for RHCS 9.0 ==> RHCS 9.1
Closed: Fixed Opened by mharmsen.

Closed: Fixed
Reopen Issue

A Wiki procedure needs to be written that documents the procedure that needs to be used to upgrade an existing RHCS 9.0 deployment running on RHEL 7.2 to an RHCS 9.1 deployment running on RHEL 7.3.

Considerations must be given for:

  • RHCS 9.0 used all 10.2.6 components from the RHCS 9 channel; RHCS 9.1 will use a combination of 10.3.3 components from RHEL 7.3 + the remainder of the 10.3.3 components from the RHCS 9 channel
  • Deployments which utilize a softokn as well as deployments which use an HSM should be considered within this document

RHCS 9.0 to 9.1 upgrade can be done using the same procedure for PKI 10.2.6 to 10.3.3 upgrade:
http://pki.fedoraproject.org/wiki/Upgrade.

Metadata Update from @mharmsen:
- Issue set to the milestone: 1.0 TASKS

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

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
None
None
None
None
Normal
defect
Wiki
Community
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.