-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
7.3.3, 7.3.4
-
7.03
-
33
-
Severity 3 - Minor
-
2
-
"Failed to start JIRA due to a build number inconsistency" when importing a Cloud backup to Server
Environment
JIRA Server 7.3.x, JIRA Cloud
Steps to Reproduce
- Obtain an XML instance backup from JIRA Cloud
- Install latest version of JIRA Server
- Attempt import of Cloud backup to Server following the steps in Migrating from JIRA Cloud to Server applications
Expected Results
Import is successful and JIRA starts normally following the import.
Actual Results
The following error message is thrown:
Failed to start JIRA due to a build number inconsistency.
The data present in your database is newer than the version of JIRA you are trying to startup.
Database build number: 100035
JIRA app build number: 73014
Please use the correct version of JIRA. You are running: 7.3.3#73014-sha1:d5be8da522213be2ca9ad7b043c51da6e4cc9754
Workaround
- Stop JIRA.
- Manually update the jira.version.patched property by directly modifying the database.
UPDATE propertystring SET propertyvalue = '<server build number>' WHERE propertyvalue = '<cloud build number>';
For example, given the above build numbers:
UPDATE propertystring SET propertyvalue = '73014' WHERE propertyvalue = '100035';
- Start JIRA normally.
- Test to ensure everything works.
Notes
Reference: JIRA Build and Version Numbers Reference