upgrade trouble, from 7.2.2 to 7.3.3 and back to 7.2.8

DrewGingery March 17, 2017

since we had add-on compatibility problems had to revert back to 7.2.8 from 7.3.3

 

Used the 'jira.downgrade.allowed=true' option and things seemed ok, for a time.

Now we notice the good ol' "JIRA Software is licensed but not currently installed" problem.

we're a standalone type system installed from tar.gz archive.

I would think the code is actually the correct version, problem seems to be this table in the DB, 'pluginversion' has some bad values in it that didn't get set back to 7.2.8

Anyone know the correct values for these records in 7.2.8 ?

image2017-3-17 15:37:6.png

 

well, actually, home_jira/plugins/installed-plugins DOES contain:

jira-software-application-7.3.3.jar

and the 7.3.0 language packs

If I just delete them and restart jira, will it repopulate the dir from the 'software' directory ?

3 answers

0 votes
jirajester September 9, 2019

We had the same issue...
downgrade from 7.13.5 to 7.10.1

what we did to resolve:

  • create pg_dump of db from jumpbox

  • create xml backup of jira

  • stop jira

  • point jira to old /opt/atlassian/jira
    • was sym linked, but removed the sym link as recommended by Atlassian
  • Create /var/atlassian/application-data/jira-config.properties

    jira.downgrade.allowed=true
  • moved all plugins from 
    /var/atlassian/application-data/plugins/installed-plugins/*
    to a backup dir
  • start jira
  • install JSW and JSD
  • install all plugins
  • restart jira
  • reindex

all good - 1hr 5m from start to QA approved

0 votes
DrewGingery March 17, 2017

unfortunately the 'issues' with the upgrade were not spotted immediately and people have been using the app all day now. fixing it without reverting to backup is the top priority.

We're fine with waiting at 7.2.8 until incompatible add-ons have been updated to work with 7.3 era code

Problem is the "JIRA Software" core component is installed as a plugin and it's the 7.3 jars and wont work with the rest of JIRA at 7.2.8

I can probably remove the 7.3 jars and replace them with the 7.2.8 jars in

atlassian-jira-software-7.2.8-standalone/atlassian-jira/WEB-INF/application-installation/jira-software-application

and manually edit the version strings in the DB

 

UPDATE:

YES, this worked fine.

 

0 votes
Niclas Sandstroem
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 17, 2017
  1. Revert to the backup you hopefully took before upgrading. Database dump, JIRA_INSTALL directory and JIRA_HOME directory.
  2. Since the difference between 7.2 and 7.3 contains some added project permissions etc. It might be so that you need to approach this differently because there might be compatibility issues.
  3. Can you live without these plugins and are you sure they will not function on 7.3.3 or any of the version released under 7.3.X?

You can see a XML export and import approach in https://confluence.atlassian.com/jirakb/after-upgrading-to-jira-service-desk-3-2-x-or-greater-service-desk-project-s-navigation-bar-shows-unable-to-render-element-due-to-an-error-845943102.html

Good luck!

      

 

Suggest an answer

Log in or Sign up to answer