Upgraded to 7.4 from 6.4.1

Question

We wanted to upgrade JIra from 6.4.14 to 7.4. In production we missed the steps of upgrading 6.4.14 to 7.0 and directly upgraded to 7.4 and got the following exception. Is there a way we can revert back to 7.0?

2017-09-26 14:03:39,436 JIRA-Bootstrap INFO      [c.a.jira.startup.JiraStartupLogger]
    
    ___ Plugin System Started _________________
    
2017-09-26 14:03:40,056 JIRA-Bootstrap INFO      [c.a.jira.upgrade.LoggingUpgradeService] run upgrades has started
2017-09-26 14:03:40,518 JIRA-Bootstrap ERROR      [c.a.upgrade.core.DefaultUpgradeTaskFactoryProcessor] Upgrade task [host,buildNumber=70024] failed
java.lang.RuntimeException: Error running original upgrade task
    at com.atlassian.jira.upgrade.AbstractUpgradeTask.runUpgrade(AbstractUpgradeTask.java:63)
    at com.atlassian.upgrade.core.DefaultUpgradeTaskFactoryProcessor.runOneUpgradeTask(DefaultUpgradeTaskFactoryProcessor.java:109)
    at com.atlassian.upgrade.core.DefaultUpgradeTaskFactoryProcessor.lambda$performUpgradesUnsafe$13(DefaultUpgradeTaskFactoryProcessor.java:80)
    at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174)
    at java.util.stream.SortedOps$RefSortingSink.end(SortedOps.java:395)
    at java.util.stream.Sink$ChainedReference.end(Sink.java:258)
    at java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:499)
    at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485)
    at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
    at java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:152)
    at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
    at java.util.stream.ReferencePipeline.findFirst(ReferencePipeline.java:464)
    at com.atlassian.upgrade.core.DefaultUpgradeTaskFactoryProcessor.performUpgradesUnsafe(DefaultUpgradeTaskFactoryProcessor.java:81)
    at com.atlassian.upgrade.core.DefaultUpgradeTaskFactoryProcessor.performUpgrades(DefaultUpgradeTaskFactoryProcessor.java:46)
    at com.atlassian.upgrade.core.DefaultUpgradeTaskManager.upgradeHostApp(DefaultUpgradeTaskManager.java:41)
    at com.atlassian.jira.upgrade.LicenseCheckingUpgradeService.executeUpgrades(LicenseCheckingUpgradeService.java:134)
    at com.atlassian.jira.upgrade.LicenseCheckingUpgradeService.runUpgrades(LicenseCheckingUpgradeService.java:97)
    at com.atlassian.jira.upgrade.ClusterLockingUpgradeService.runUpgrades(ClusterLockingUpgradeService.java:35)
    at com.atlassian.jira.upgrade.LoggingUpgradeService.lambda$runUpgradesWithLogging$0(LoggingUpgradeService.java:28)
    at com.atlassian.jira.upgrade.LoggingUpgradeService.runWithTaskLogging(LoggingUpgradeService.java:43)
    at com.atlassian.jira.upgrade.LoggingUpgradeService.runUpgradesWithLogging(LoggingUpgradeService.java:28)
    at com.atlassian.jira.upgrade.IndexingUpgradeService.runUpgrades(IndexingUpgradeService.java:19)
    at com.atlassian.jira.upgrade.DefaultUpgradeService.runUpgrades(DefaultUpgradeService.java:56)
    at com.atlassian.jira.upgrade.UpgradeLauncher.upgradeIfNeeded(UpgradeLauncher.java:109)
    at com.atlassian.jira.upgrade.UpgradeLauncher.start(UpgradeLauncher.java:87)
    at com.atlassian.jira.startup.ActiveServicesLauncher.start(ActiveServicesLauncher.java:50)
    at com.atlassian.jira.startup.DefaultJiraLauncher.postDBActivated(DefaultJiraLauncher.java:181)
    at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$2(DefaultJiraLauncher.java:155)
    at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:304)
    at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:199)
    at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:146)
    at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:105)
    at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
    at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:103)
    at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:157)

Anubha Bhardwaj · Answer

Thanks for responding.We rolled back and we will upgrade again

6.4.14 -> 7.0 -> 7.4

Andy Heinzer · Answer

It depends on what the upgrade has already done.  We know this upgrade task has failed, but if other upgrade tasks were already executed successfully, then likely there is data in the Jira database that is already updated for the 7.4 database scheme.   If that happens, it's not so simple to just jump back to a 7.0 version without restoring the database with a backup.

The clearest solution here would be to revert the changes this upgrade attempt has done by following the steps in Rolling back a Jira upgrade

But that guide expects you to have a database backup (or XML backup) taken before the upgrade, as well as copies of the JIRA_INSTALL and JIRA_HOME folders.   The install folder usually isn't as important as you can typically just use the installation package to replace that, but the Jira home folder contains all your plugins and more importantly, your attachments/avatars.

If you have a backup of the database and the JIRA_HOME files, then you technically don't have to reinstall 6.4.14, you could actually install a 7.0.x version fresh, and then connect your home directory to this, and in turn restore your database.   But I wouldn't suggest using the existing database as it likely is stuck in a semi-broken state due to this upgrade attempt.

Josh Steckler · Answer

It is likely you will need to restore from backups and get your instance running on 6.4.1 again.