Jira upgrade only upgrading jira core. Not upgrading jira software.

[Munjal Patel]

Upgrading jira with following command:

     helm upgrade -i testjira01 jira-1.0.0.tgz  --namespace testnamespace --version 1.0.0 \

     --values cicd/test/values.yaml --reuse-values --set replicaCount=1 -set image.tag=8.19.1

above upgrade command only upgrades jira core. Jira software version stays same.

Clicking update button via UI to update Jira software gives unexpected error.

Below lets me install jira-software:

1. Stop Jira
2. Go to the <Jira-Shared-Home>/plugins/installed-plugins directory
3. Rename the <Jira-Shared-Home>/plugins/installed-plugins directory to <Jira-Shared-Home>/plugins/installed-plugins2
4. Start Jira
5. Install Jira Software via UI.

Tried normal and rolling upgrade both do not upgrade jira-software plugin.

Image is downloaded using "docker pull atlassian/jira-software:8.19.1"  from docker hub and pushed to ACR and tagged properly. Jira is running on AKS and shared files folder storage class is azurefiles.

[Yevhen]

Hi @Munjal Patel 

I think you may need to take a look at:

* https://atlassian.github.io/data-center-helm-charts/userguide/CONFIGURATION/#additional-libraries-plugins

* https://github.com/atlassian/data-center-helm-charts/blob/main/src/main/charts/jira/values.yaml#L568

In other words, your installed plugins need to be persisted across pod restarts.

[Munjal Patel]

jira-software is installing following plugins for 8.18.2 version. Many of them have version number in .jar file name and they may change when we upgrade so helm upgrade should update them instead of me listing them in values files?

plugins/installed-plugins-jira-software/jira-bamboo-plugin-8.18.2.jar
plugins/installed-plugins-jira-software/jira-development-integration-plugin-5.10.3.jar
plugins/installed-plugins-jira-software/jira-dvcs-connector-plugin-5.7.2.jar
plugins/installed-plugins-jira-software/jira-fisheye-plugin-8.18.2.jar
plugins/installed-plugins-jira-software/jira-greenhopper-plugin-8.18.2.jar
plugins/installed-plugins-jira-software/jira-portfolio-8.18.2.jar
plugins/installed-plugins-jira-software/jira-software-application-8.18.2.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-cs_CZ-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-da_DK-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-de_DE-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-en_US-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-es_ES-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-et_EE-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-fi_FI-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-fr_FR-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-hu_HU-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-is_IS-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-it_IT-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-ja_JP-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-ko_KR-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-nl_NL-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-no_NO-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-pl_PL-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-pt_BR-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-ro_RO-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-ru_RU-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-sk_SK-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-sv_SE-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-language-pack-zh_CN-8.15.0.20210614004853.jar
plugins/installed-plugins-jira-software/jira-software-monitor-plugin-8.18.2.jar
plugins/installed-plugins-jira-software/jira-software-plugin-8.18.2.jar
plugins/installed-plugins-jira-software/jira-transition-triggers-plugin-8.18.2.jar
plugins/installed-plugins-jira-software/portfolio-plugin-8.18.2.jar
plugins/installed-plugins-jira-software/querydsl-4.0.7-provider-plugin-1.2.jar
plugins/installed-plugins-jira-software/team-management-plugin-8.18.2.jar

My understanding was additional-libraries-plugins is not for jira-software. That is for marketplace plugin. We use alternative to this method to install the plugins via "Manage Apps" in the product system administration UI. 

[Yevhen]

@Munjal Patel yes, sorry I did't pay attention that it's a shared home directory. Upgrade of a Helm chart is about pulling and running a new image of Jira Software.

Can you please share a screenshot of what you see in UI after the upgrade? What happens in K8s does not differ from Jira upgrade in a VM world - new Jira software binaries run and an upgrade happens. 

[Munjal Patel]

[Dylan Rathbone]

@Munjal Patel additionally was your original helm deployment (before performing the upgrade) for Jira software or Jira core? Can you also supply the values.yaml you used for performing the original deployment including the helm command used for deploying.

[Munjal Patel]

Jira Software original helm deployment before performing the upgrade.

Same helm command with different image tag. Original install and upgrade is done using gitlab ci/cd so just changed version number var between them. We are using helm upgrade -i option.

[Yevhen]

@Munjal Patel I have just checked:

* a fresh 8.19.0 installation

* upgrade to 8.19.1

Both Jira software and core were correctly updated. I wasn't able to reproduce the issue. Do you have a sandbox environment to try the same scenario i.e. a fresh deployment and an upgrade?

And as @Dylan Rathbone suggested, sharing your custom values will help too.