Jira Service Desk: weird version mismatch errors in logs

levigo systems

Hi,

following issue occurs in a customer's environment with Jira 7.13.11 and JSD 3.16.11:

JSD behaves erratically, Projects can be created but noot loaded and so on:

Log shows:

2020-08-05 18:11:46,096 JIRA-Bootstrap INFO [bootstrap.lifecycle.server.ServerPluginLifeCycle] Checking license...
2020-08-05 18:11:46,222 JIRA-Bootstrap INFO [bootstrap.lifecycle.server.ServerPluginLifeCycle] Check if upgrade requirements are satisfied...
2020-08-05 18:11:46,331 JIRA-Bootstrap ERROR [bootstrap.lifecycle.server.ServerPluginLifeCycle] '1.2.7' version of Service Desk cannot be upgraded to '3.16.11-REL-0002'. Upgrade to '3.0.0' <= <version> < '3.2.0' first.
com.atlassian.servicedesk.bootstrap.lifecycle.server.UnsatisfiedVersionRequirementException: '1.2.7' version of Service Desk cannot be upgraded to '3.16.11-REL-0002'. Upgrade to '3.0.0' <= <version> < '3.2.0' first.
at com.atlassian.servicedesk.bootstrap.lifecycle.server.UpgradeRequirementsChecker.checkVersionRequirementForUpgrade(UpgradeRequirementsChecker.java:47)
 at com.atlassian.servicedesk.bootstrap.lifecycle.server.ServerPluginLifeCycle.checkAndRunUpgrades(ServerPluginLifeCycle.java:249)
at com.atlassian.servicedesk.bootstrap.lifecycle.server.ServerPluginLifeCycle.start(ServerPluginLifeCycle.java:209)

<snip>


 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 java.lang.Thread.run(Thread.java:748)
2020-08-05 18:11:50,576 JIRA-Bootstrap INFO [automation.internal.bootstrap.AutomationPluginLauncher] AutomationPlugin onStart() - Service Desk Automation Plugin is starting...
2020-08-05 18:11:51,442 JIRA-Bootstrap INFO [automation.internal.bootstrap.AutomationPluginLauncher] AutomationPlugin onStart() - Service Desk Automation Plugin is started.

 

Directory installed-plugins shows:

root@service:/var/atlassian/application-data/jira/plugins# ls -art installed-plugins/*service*
installed-plugins/servicedesk-core-ui-plugin-3.16.11-REL-0002.jar
installed-plugins/servicedesk-canned-responses-plugin-3.16.11-REL-0002.jar
installed-plugins/servicedesk-project-ui-plugin-3.16.11-REL-0002.jar
installed-plugins/servicedesk-automation-then-webhook-plugin-3.16.11-REL-0002.jar
installed-plugins/jira-servicedesk-public-rest-api-plugin-3.16.11-REL-0002.jar
installed-plugins/servicedesk-lingo-plugin-3.16.11-REL-0002.jar
installed-plugins/servicedesk-automation-modules-plugin-3.16.11-REL-0002.jar
installed-plugins/servicedesk-reports-plugin-3.16.11-REL-0002.jar
installed-plugins/servicedesk-internal-base-plugin-3.16.11-REL-0002.jar
installed-plugins/servicedesk-notifications-plugin-3.16.11-REL-0002.jar
installed-plugins/servicedesk-automation-plugin-2.13.0.jar
installed-plugins/servicedesk-approvals-plugin-3.16.11-REL-0002.jar
installed-plugins/servicedesk-frontend-plugin-3.16.11-REL-0002.jar
installed-plugins/servicedesk-knowledge-base-plugin-3.16.11-REL-0002.jar
installed-plugins/jira-servicedesk-3.16.11-REL-0002.jar
installed-plugins/servicedesk-search-plugin-3.16.11-REL-0002.jar
installed-plugins/servicedesk-variable-substitution-plugin-3.16.11-REL-0002.jar
installed-plugins/jira-servicedesk-application-3.16.11.jar

 In what way is this a version mismatch, as the official list shows 7.13.11 should be fine with 3.16.11.

One of my guesses is, if upgrading to 7.13.16 and 3.16.15 possibly mitigate the issue?

Petter Gonçalves

Hello @levigo systems

Thank you for reaching out.

Can you confirm if the problem started when you updated your Service Desk or Jira Core?

Analyzing the logs of the error returned, it seems that the current version of your Jira Service desk does not have the minimum upgrade requirements:

UnsatisfiedVersionRequirementException

This error usually happens when you try to upgrade from a far older version that does not have the required features to upgrade to the most recent version of the application.

In order to fix this behavior, you must ensure your Jira Service desk was upgraded to version 3.0.x/3.1.x first, and your Jira core to 7.0.x.

Please, take a look at the documentation below so you can check the steps to rollback your product version and fix the problem:

Unable to render element error in navigation bar after upgrading Jira Service Desk 

Please, let us know if you have any questions about the steps provided in the documentation.