Hi there, I’m trying to upgrade my SonarQube instance to the latest version. I’ve upgraded successfully from 6.7 to 6.7.5, but I’m not able to upgrade to 7.3. When hitting the /setup URL, I’m having the exception (in the web.log): 2018.08.21 21:41:03 ERROR web[][o.s.s.p.d.m.DatabaseMigrationImpl] …

Hi Eric, Do you have more logs after at java.lang.Thread.run(Unknown Source) ? Regards

I’m attaching everything I have. Thanks for having a look.

I guess my attachment didn’t go to the forum. Also is too small to past the full log… 2018.08.21 21:38:36 INFO web[][o.s.s.p.d.m.s.MassUpdate] 1240 snapshots processed (0 items/sec) 2018.08.21 21:39:36 INFO web[][o.s.s.p.d.m.s.MassUpdate] 1240 snapshots processed (0 items/sec) 2018.08.21 21:40:36…

After creating the index manually just to try to go through the upgrade process, I’ve got an issue with duplicated keys related to Azure AAD plugin. Azure AAD plugin fills the fields external_id with “Azure AD”. So, id duplicates external_identity_provider and external_id. I’m not sure if this is a…

Another issue with trying to create an index with the same name: 2018.08.22 11:47:32 ERROR web[][o.s.s.p.d.m.DatabaseMigrationImpl] DB migration failed | time=82ms 2018.08.22 11:47:32 ERROR web[][o.s.s.p.d.m.DatabaseMigrationImpl] DB migration ended with an exception org.sonar.server.platform.db.mi…

This issue has already been reported there : [image] SQ 7.2. DB schema migration fails SonarQube Server / Community Build This issue is on Azure Active Directory plugin side, as it should set unique identifier as external ID, not “Azure AD”. Please open a Github issue to …

Hi Julien, I understand that the failures 2 and 3 are related to Azure AD. But the first one, is definitely not. I don’t think this will sort out all the issues on the upgrade. Regards, Eric

It seems that there’s an issue on your database, because it seems that you had to manually add DB Index, which should never happen. I would recommend you to restore your DB to the state before the upgrade, and try to understand why SonarQube was not able to drop/create indexes.

Upgrade from 6.7 to 7.3 failed

SonarQube Server / Community Build

AndrewG (Andrew) August 22, 2018, 10:16pm 9

I have the same issue, Upgrading from v7.0.0 to v7.1.2, upon startup cant auth to Azure SQL Server using old jdbc string

Topic		Replies	Views
SonarQube 7.3 database upgrade failed on #2114 'Add unique indexes on table users' SonarQube Server / Community Build bug-no-category	1	1633	September 16, 2018
ERROR Upgrade from 6.7.6 LTS to version 7.9.1 LTS : ERROR web[][DbMigrations] Executed DB migrations: failure \| time=47ms SonarQube Server / Community Build sonarqube , upgrade , mssql , migration	8	1629	February 17, 2020
Upgrading sonarqube community edition from version 6.7.7 to 7.9.3 Drop unique index on QUALITY_GATES.NAME': failure SonarQube Server / Community Build upgrade	2	538	July 14, 2020
SQ 7.2. DB schema migration fails SonarQube Server / Community Build sonarqube , upgrade	13	4305	October 30, 2019
Upgrade SonarQube version 6.7.2 (build 37468) to version 7.9.1 failed in migration step SonarQube Server / Community Build sonarqube	2	1243	July 23, 2019

Upgrade from 6.7 to 7.3 failed

Related topics