-
Bug
-
Resolution: Fixed
-
High
-
5.1.2, 5.1.3, 5.1.4, 5.1.5, 5.2, 5.2.3, 5.2.5, 5.3, 5.3.1, 5.4
-
None
In-place upgrades of Confluence Clustered installations doesn't work, and hasn't worked since Confluence 5.1.2.
To reproduce:
- Setup 2 nodes of a Confluence 5.0.x clustered installation
- Shutdown the nodes
- Upgrade node 1 to Confluence 5.4, verify that the database is upgraded as expected
- Upgrade node 2 also, note that startup fails due to "the build number in the home directory [4109] doesn't match the build number in the database [4723]"
Upgrading cluster installations to any version prior to 5.1.2 works fine, but upgrading any cluster installations to 5.1.2 or later will likely fail.
Importantly, this only affects Confluence clustered installations, and only those being upgraded from one version to another using in-place upgrades rather than site imports.
- is caused by
-
CONFSERVER-13798 Prevent Confluence startup if version of home directory and database do not match (to stop inadvertent attempt to upgrade via database backup)
- Closed