Notification of database upgrade

[pki-bot]

This issue was migrated from Pagure Issue #998. Originally filed by edewata (@edewata) on 2014-05-09 19:32:27:

• Closed as Fixed
• Assigned to edewata (@edewata)

---

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

[pki-bot]

Comment from mharmsen (@mharmsen) at 2014-05-19 20:34:14

Per PKI/389 Meeting of 05/19/2014, moving to Milestone 10.2 (May).

[pki-bot]

Comment from edewata (@edewata) at 2014-05-21 23:26:10

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.

[pki-bot]

Comment from edewata (@edewata) at 2014-05-22 14:41:37

master: 8618fa8

[pki-bot]

Comment from edewata (@edewata) at 2017-02-27 14:08:21

Metadata Update from @edewata:

• Issue assigned to edewata
• Issue set to the milestone: 10.2 - 05/14 (May)