which versions are you using (SonarQube Server / Community Build, Scanner, Plugin, and any relevant extension)
Old image version: 25.12.0.117093-community (working)
New image version: 26.5.0.122743-community (broken)
how is SonarQube deployed: zip, Docker, Helm
Docker image in kubernetes cluster (oracle cloud) with physical volumes for data etc.
what are you trying to achieve
perform an update of sonarqube
what have you tried so far to achieve this
replace the image tag with the new one
The error I got was that I was upgrading from an older version than 25.12 is not possible but it was a 25.12 version. So I am a bit confused if that is actually a bug or some misconfiguration on my side.
I have the same behavior. I successfully upgraded to `sonarqube:25.12.0.117093-community` with the Docker image and a PostgreSQL-DB. If I now try to upgrade to `sonarqube:26.5.0.122743-community` I get the same error - I should first upgrade to 25.12. But I have already upgraded to 25.12.!
I found some information I should first upgrade to `sonarqube:26.3.0.120487-community`, but I receive the same error here.
Did someone already update from 25.12.0 to a 26.x.0 with PostgreSQL and a successful result?
If I look into the DB table for the version by `SELECT version FROM schema_migrations ORDER BY version::bigint DESC LIMIT 5;`. I will recieve these entries:
Now I saw in the release notes that with version 26.2.0.119303 the support for my PostgreSQL DB is dropped (v12.3).
Which PostgreSQL do you use?
**PostgreSQL18 support**
Support for PostgreSQL versions is now from 14 to 18, enabling deployments using the most recent PostgreSQL release. Support for version 13 has been removed.
In my case, the image for postgres cluster nodes is Package spilo-18 · GitHub, which means that we have PostgreSQL 18. I don’t thinks that there is a problem with Postgres as v18 seems to be working fine with 25.12.
I’m not sure if PostgreSQL 18 works for this update because your current version 25.12. do not support PostgreSQL 18. I know you do the updates with the new 26.x but I don’t know if this is really tested.
maybe that is how it should be done? That you use .1 as an intermediate release before going to 26.5? As for me, it looks more like a migration path issue.
Generally, you would have to go to the xx.12 version before you could move to the next year, but there’s a bug in 25.12, so 25.x → 26.1 is (exceptionally) a valid path.
upgrade from 25.12 to 26.1 did succeed, so yes, there seems to be an issue with the upgrade path. I can confirm that the server is now running on 26.5 as going from 26.1 seems to be successful.
.