Error related to zero downtime support during upgrade

[Martin McCann]

Hello
I am upgrading Jira Sottware from 7.13.12 to 8.5.4  (to the latest Enterprise Release)

- performed backups
- download atlassian-jira-software_x64.binn  for Linux  (version 8.5.4)
- performed upgrade
- reinstated config changes into the new version (server.xml, setenv.sh, catalina.sh etc)
- start-jira.sh

  I tail the log and see this exception below that Jira cannot start...  (see Result)
  in /opt/atlassian/jira/software/application-data/jira/log/atlassian-jira.log
  PLEASE ADVISE ON WHAT ACTION I CAN TAKE.? Do I need to revert back to pre-upgrade
  snapshots and upgrade again or is there a workaround...

 Thank you /Martin
 
 Result:

2020-04-09 07:17:34,868-0400 localhost-startStop-1 ERROR [c.a.jira.startup.LauncherContextListener] Unable to start JIRA.
java.lang.IllegalStateException: Your node with Jira version 8.5.4 will not start up with version 7.13.12 because Jira does not support zero downtime upgrades between major releases. See https://docs.atlassian.com/jira/jadm-docs-080/Upgrading+Jira+applications.
at com.atlassian.jira.startup.ClusterNodeVersionCheckLauncher.verifyMajorVersion(ClusterNodeVersionCheckLauncher.java:85)
at com.atlassian.jira.startup.ClusterNodeVersionCheckLauncher.start(ClusterNodeVersionCheckLauncher.java:71)
at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$postDbLaunch$2(DefaultJiraLauncher.java:144)
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrEnqueue(DatabaseConfigurationManagerImpl.java:301)
at com.atlassian.jira.config.database.DatabaseConfigurationManagerImpl.doNowOrWhenDatabaseActivated(DatabaseConfigurationManagerImpl.java:196)
at com.atlassian.jira.startup.DefaultJiraLauncher.postDbLaunch(DefaultJiraLauncher.java:137)
at com.atlassian.jira.startup.DefaultJiraLauncher.lambda$start$0(DefaultJiraLauncher.java:104)
at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:31)
at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:102)
at com.atlassian.jira.startup.LauncherContextListener.initSlowStuff(LauncherContextListener.java:154)
at com.atlassian.jira.startup.LauncherContextListener.initSlowStuffInBackground(LauncherContextListener.java:139)
at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:101)
... 5 filtered

[Daniel Ebers]

Hi Martin,

welcome to Atlassian Community!

From documentation an upgrade from Version 7 to Version 8 cannot be done using Zero Downtime Upgrade. One of the regular methods have to be used.

This is very likely the cause of the error message you are seeing.

Please also check documentation linked below.
https://confluence.atlassian.com/adminjiraserver/upgrading-jira-data-center-with-zero-downtime-938846953.html

Cheers,
Daniel

[Martin McCann]

HI Daniel
Thank you... just two final questions please :
==

1. I performed all the steps including Step 2. (Optional) Update Jira Service Desk
The Jira page is rendering showing the new log... and it says Jira in the top left
(not Jira Software)
I installed JSD using the UI and installed a license for it..

My question is: Is JSD suppose to be integrated into jira in ONE instance in this later release,  is this the way it is designed in thislater release?

The reason I ask is because in my original release 7.13.12 (3.16.12 JSD)...we installed
JSW and JSD as two seperate instances and using two seperate URLs where we can
select between JSW and JSD in the UI (top left)

i.e. on each node (two instance)
su - jsw_user and then start-jira.sh
su - jsd_user and then start-jira.sh
JSW - http://<node1>:9445
JSD - https://<node1>:9443

Can I uninstall JSD from the UI and use the installer .bin to install it as a seperate instance as before? as we have seperate MySql databases for each also?

2. Copying JSW to other nodes as a template
When I installed Jira on node 1 the existing installation directory was
/opt/atlassian/jira/software/current
I zipped this folder up on node1 and on node2 I extracted it from / ..
jira starts but I get a HTTP 404 when I hit the URL https://<node2>:9445
The reinstated changes were the same..

Question: ... Is the above correct?   copy  /opt/atlassian/jira/software/current
as a template?
Can I use the installer on node2 for installing JSW if desired?
Revert to previous snapshot for node2 , shutdown jira completely on the cluster
and install (using .bin) on node2?

[Martin McCann]

Daniel

What is the new installation directory mentioned in this step below?
Is it the updated /opt/atlassian/jira/software/current  to be zipped up and used as
a template?

Step 5. Copy the upgraded Jira as a template

In this step, you'll copy the new installation directory with all the modifications you did so far. This will give you a template that you'll later copy to other nodes.

1. Copy the new installation directory to some other location. This will be your template.