If someone has an existing Dogtag installation, a manual database upgrade will be required to use the latest version of Dogtag. While the upgrade process itself will be documented in wiki page or in embedded docs, people might not be aware of this requirement especially if the RPM is upgraded automatically by yum. Without the database upgrade some Dogtag functionalities may no longer work.
One option is to show the link to the docs after RPM upgrade, but people could still miss it. Another option is to add database version, then check the version during startup, and fail if the database is not upgraded yet (ticket #906).
Proposed milestone: 10.2 May
Per PKI/389 Meeting of 05/19/2014, moving to Milestone 10.2 (May).
Per discussion with alee, since the database upgrade is irrelevant to IPA, and the changes are only needed for certain deployment configuration, for now the notification can just be documented in a README file.
master: 8618fa8837df51938acf7cd8b02112eef51dde44
Metadata Update from @edewata: - Issue assigned to edewata - Issue set to the milestone: 10.2 - 05/14 (May)
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/1564
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.
Login to comment on this ticket.