how is SonarQube deployed: Docker image hosted to Web App with azure sql database server via Azure Bicep
what are you trying to achieve: make sure server id stays the same
what have you tried so far to achieve this: checking sonarqube web instance app configuration, check database audit logs to see if someone changed the resource
Issues:
We used to run SonarQube 8.9 developer for a long. Quite stable. Monday this week I upgraded the docker image version to 10-developer. After that, the server ID got reset. The first time might make sense. However, this week Thursday and now Friday, the server id gets reset again without any changes from our infrastructure side.
During the upgrade, what I have done was only changing the image version from 8.9-developer to 10-developer for a more powerful version.
However, because of server id keeps changing, I need to reconfigure each time the service connection, regenerate PAT, user permissions, etc.,
Please give insights of what would be the cause. I attached the app configuration in case you find any related causes.
In our case, the bicep deployment should not create a new db since it performs as add or update. The URL has not been touched. It is a mystery why the serverID had been refreshed. Anything you logged that could trigger serverID refresh? If so, I can monitor the logs.
If all you’re changing is the image being used (and none of the other configuration), you may have missed that the environment variables prefixed with SONARQUBE_ no longer work (and your instance is probably falling back on the internal H2 database). This is noted in this upgrade note:
The deprecated SONARQUBE_JDBC_USERNAME, SONARQUBE_JDBC_PASSWORD, and SONARQUBE_JDBC_URL variables have been removed. See Environment variables for up-to-date configuration variables.
You will need to use SONAR_JDBC_USERNAME, SONAR_JDBC_URL, AND SONAR_JDBC_PASSWORD instead.
Also keep in mind that to perform an upgrade from 8.9 to 10.2, you’ll have to make a stop at 9.9.
It’s necessary to stop at intermediate LTS versions, as once the major version ticks over, the database migrations are no longer included for previous versions.