Jira upgrade failed using docker

[Muhammad Ramzan_Atlassian Certified Master_]

I am using Jira on docker. I upgraded the jira from 8.6 to 8.8 version. I have configured volume for jira home.

Upgrade: Custom changes have not been carried over

The listed configuration files contain custom changes. To keep your current configuration, re-apply these custom changes to the new version of the files during upgrade.I following following steps:

bin/setenv.s

1- docker-compose down

2- Change the jira image version to 8.8

3- docker-compose up -d

I have installed plugins and settings in in 8.6 before. 

How i can do this change which jira is referring, since we are in container and container is can be down and up any time.

[Andy Heinzer]

Hi @Michael Kriese 

Thanks for pointing that out again.  I took another look at this and I think I see what is happening here.  I took a hard look at the differences between the 8.10.0 and 8.11.0 setenv.sh files for fresh installs (non docker installs).  They both have the same number of characters in them. 

However on line 68 of the setenv.sh file appears to now have a dynamic URL that is echoed to the terminal if Jira fails to start up.   While this is not really a configuration change, it will change the md5 hash of that file upon each major and minor Jira upgrade.  And since the healthcheck is looking for any md5 hash difference, it's incorrectly flagging this file as having some kind of change for these upgrades.

This appears to happen for nearly all Jira 8 upgrades, except for point release upgrades (such as 8.5.0 to 8.5.1).  I have created a new bug for this over in JRASERVER-71338.  

Sorry for the inconvenience here.  Chances are this warning is a false positive of that health check.

Andy

[Andy Heinzer]

Hi Muhammad,

I understand that you're using Docker in order to attempt to upgrade Jira server to 8.8.  However in the process of doing this you are seeing a warning that some customizations will not be carried over.

That particular file, the $JIRAINSTALL/bin/setenv.sh file tends to get overwritten upon each upgrade of Jira.  This file controls the environmental setting such as the JVM startup flags which can set how much memory heap Jira can use when it starts up and other option flags.  Essentially, if you need to make changes to that file in the docker, you need to open a terminal to that operating system that the docker is running.  I suspect this is some Linux distro, but I'm not sure which one.

The help guide over in https://hub.docker.com/r/atlassian/jira-software explains under the manual diagnostics section how you can do this:

The jcmd utility is also included in these images and can be used by starting a bash shell in the running container:

docker exec -it my_container /bin/bash

This is one means from within your host machine running docker that you could get a bash shell for that container.  From there you could use a command such as

nano /opt/atlassian/jira/bin/setenv.sh

Perhaps you might have to sudo before that, but maybe not. That shell should then let you make changes to that configuration file as needed.  Once you save changes to that file, you will need to save that file. If Jira is currently running, you would need to restart the Jira application in order for those changes to be applied.

I hope this helps.

Andy

[Michael Kriese]

@Andy Heinzer I never changed that file manually (using the official docker images too), why is jira complaining about it?

Does the docker build script editing that file?

Happend to me while upgrading from 8.10 to 8.11.