#2239 [WIKI] Database upgrade procedure for PKI 9 server
Closed: migrated by dmoluguw. Opened by edewata.

When PKI 9 server is cloned into PKI 10, the PKI 10 server will use the replicated PKI 9 database. The problem is the replicated PKI 9 database might be missing some database entries that are required by PKI 10 server (e.g. ACL for REST API), so some operations in PKI 10 server might fail (e.g. authorization errors).

To fix the problem, the database needs to be upgraded such that it works for both PKI 9 and 10 servers.

The current database upgrade procedure is documented here:
http://pki.fedoraproject.org/wiki/Database_Upgrade

It needs to be updated to include the upgrade procedure from PKI 9 to 10.

See also ticket #1000.


Per CS/DS Triage Meeting of 03/22/2016: 10.3 Backlog

Upgrading an existing database (without cloning) will not be useful without the ability to install a new instance using the upgraded database (ticket #2325).

For now the migration can be done using export and import:
http://pki.fedoraproject.org/wiki/Migrating_a_CA_with_HSM_using_existing_CA_mechanism

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

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

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