Currently the server configuration is upgraded automatically when the RPMs are upgraded. When the server is restarted by the admin it will use the upgraded configuration.
With the addition of database upgrade, automatic upgrade might not be appropriate for all situations since a database upgrade might have a system wide impact. It might take sometime to run, and the changes might not be reversible (LDAP delete operations cannot be undone without creating a backup first).
Dogtag could provide some options to the admin, but we need to decide what should be the default behavior of Dogtag out of the box.
See the following page: http://pki.fedoraproject.org/wiki/Upgrade_Process
This is required for CA migration.
Metadata Update from @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/1476
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
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)
Login to comment on this ticket.