Jira Version Behind Database Version

[Jason Hamilton]

So I'm running Jira in Docker.  According to the build sites I should be on 80009 but my database is apparently on 80009 and my Jira is on 80007.

Checking in the database I see

MariaDB [jira]> select * from propertystring where id = (select id from propertyentry where property_key = 'jira.version');
+----+---------------+
| ID | propertyvalue |
+----+---------------+
| 13 | 8.0.1 |
+----+---------------+
1 row in set (0.001 sec)

I've had docker pull the image fresh to ensure that I'm on the latest version which should match my database but I'm still stuck.

Thank you all for your help with this and if there is anything I can provide to help solve this please let me know.  

[Andy Heinzer · Accepted solution]

Well, It looks like your Jira database was at least run once against a Jira 8.0.1 version.  That is the only way I can figure why you might have a Jira build number of 80009, but your application could still be 8.0.0 (80007).  However what is odd about this is that the 8.0.1 version has been pulled off the download site by Atlassian due to a pretty bad bug that would specific affect Jira Service Desk functions failing when connected to a Microsoft SQL database on the back end.

I'm not sure where your docker distro is getting these distributions though.  Atlassian does not yet offer a docker image for Jira deployments officially.  However since 8.0.1 was pulled from downloads, there is a 8.0.2 version that has been released that fixes that and some other bugs.

Maybe the docker image also reverted down to the 8.0.0 version when the 8.0.1 was pulled from Atlassian's official download channels?  I'm not sure that is what happened in your case, but it might be a factor here.

[Jason Hamilton]

Yeah I guess watchtower picked it up instantly when it was made available.  Might need to rethink how I want to handle updates of Jira in the future :).  Right now watchtower just picks it up and runs with it.