Server ID Issues Post Server and DB Upgrade running on Kubernetes

SonarQube Server / Community Build
,
1
  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension): Sonarqube 9.7, 9.9, 10, 10.7
  • how is SonarQube deployed: Helm
  • what are you trying to achieve: uprgade without getting new license
  • what have you tried so far to achieve this: upgrading DB for compatibility and also the server version to various others

We seem to be having an issue when upgrading Sonarqube running on K8s deployed via helm that whenever we take any action, the server ID is regenerated, causing us to need a new license.

Is there a definitive/recommended best practice to avoid this happening on K8s installations?
We have made sure that the JDBC url appears to be exactly the same in the environment variable etc, but were surprised to see that we couldnt get the server ID to stay the same.

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

2

Hey there.

Are you fully redeploying the database from scratch? When that happens, the Server ID gets refreshed.

From the docs on License Administration:

Actions that will invalidate your license key

  • Restoring the database content from another SonarQube instance (except for production/staging synchronization).
  • Reinstalling SonarQube on an empty database.
3

We were upgrading the existing database to a newer version of postgresql, hosted on RDS.