Missing projects when upgrading SonarQube 6.7.3 to SonarQube 6.7.7

I found that some projects are missing after upgrading SonarQube 6.7.3(Community Edition) to SonarQube 6.7.7(Community Edition). The database of my SonarQube instance is MySQL v5.7.28.

The migration is part of the whole process of upgrading to SonarQube 7.9.2(LTS)
As MySQL is not supported in SonarQube 7.9.2, I have to go through the upgrade path as follow.
SonarQube 6.7(MySQL) → SonarQube 6.7.7(MySQL) → SonarQube 6.7.7(PostgreSQL) → SonarQube 7.9.2(PostgreSQL).

However, I found that most of the projects in the original SonarQube 6.7.3 are missing after upgrading to SonarQube 6.7.7.

Is there any workaround to overcome the matter? Any suggestion is welcomed.

BTW, I have made sure the data and temp folders are empty when starting SonarQube 6.7.7 instance.


You didn’t actually have to upgrade to 6.7.7 on your way to 7.9.2, but it shouldn’t hurt anything that you did.

Off-hand it sounds like a corrupt Elasticsearch index. Normally for that you’d delete $SONARQUBE-HOME/data/es5 and restart, but you’ve already done that? And projects - only some of them? - were still missing after startup?

When you say ‘missing’, that means you don’t see them on the Projects page? You can’t search for them in the global (top-right) search bar? Can’t navigate to them via bookmarks/browser memory?


Thanks @ganncamp.

Yes, after I upgrade SonarQube 6.7.3(MySQL) to SonarQube 6.7.7(MySQL), most of the projects are missing. Originally, the SonarQube 6.7.3 has 32 projects, after upgrading, SonarQube 6.7.7 only has 1 project left.

As my ultimate goal is to upgrading to SonarQube 7.9.2(PostgreSQL), the above issue was actually addressed by changing the upgrade path as follow.
SonarQube 6.7.3(MySQL) —> SonarQube 6.7.3(PostgreSQL) --> SonarQube 7.9.2(PostgreSQL).

No project will be lost after using the new upgrade path.