AKS Load Balancer Health Probe Issue

SonarQube Server / Community Build
1

Must-share information (formatted with Markdown):

  • which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
    We are using SonarQube Version: 9.0.0-enterprise
  • how is SonarQube deployed: zip, Docker, Helm
    We are deploying the Postgres DB, nginx-ingress and SonarQube using helm chart.
  • what are you trying to achieve
    After I deploy the sonarqube using helm chart in AKS, I observed that the Load Balancer health Probe are creating unhealthy (/). We are using liveliness probe, readiness probe and startup probe configuration.
readinessProbe:
tcpSocket:
port: 8080
initialDelaySeconds: 60
periodSeconds: 30
failureThreshold: 6
If an ingress *path* other than the root (/) is defined, it should be reflected here
A trailing “/” must be included
sonarWebContext: /
sonarWebContext: /sonarqube/

livenessProbe:
tcpSocket:
port: 8080
initialDelaySeconds: 60
periodSeconds: 30
failureThreshold: 6
If an ingress *path* other than the root (/) is defined, it should be reflected here
A trailing “/” must be included
sonarWebContext: /
sonarWebContext: /sonarqube/
If an ingress *path* is defined, it should be reflected here
sonar.web.context: /sonarqube

startupProbe:
initialDelaySeconds: 30
periodSeconds: 10
failureThreshold: 24
If an ingress *path* other than the root (/) is defined, it should be reflected here
A trailing “/” must be included
sonarWebContext: /
sonarWebContext: /sonarqube/
  • what have you tried so far to achieve this
    We have manually added health probes pointing to TCP and whenever the POD is getting restarted the health probe is going back to unhealthy state.
Pods:
NAME                                                  READY   STATUS    RESTARTS         AGE
sonarqube-ingress-nginx-controller-#####-####   1/1     Running   0                9d
sonarqube-postgresql-0                                1/1     Running   0                26d
sonarqube-sonarqube-0                                 1/1     Running   11 (7d21h ago)   26d

Here is the sonarqube-sonarqube-0 logs.

2024.03.08 11:48:09 INFO  web[AY4FlAcFB/KA6OylAHYD][o.s.u.c.UpdateCenter] The plugin 'securitycsharpfrontend' version : 9.0.0.12669 has not been found on the update center.
2024.03.08 11:48:09 INFO  web[AY4FlAcFB/KA6OylAHYD][o.s.u.c.UpdateCenter] The plugin 'securityjavafrontend' version : 9.0.0.12669 has not been found on the update center.
2024.03.08 11:48:09 INFO  web[AY4FlAcFB/KA6OylAHYD][o.s.u.c.UpdateCenter] The plugin 'securityjsfrontend' version : 9.0.0.12669 has not been found on the update center.
2024.03.08 11:48:09 INFO  web[AY4FlAcFB/KA6OylAHYD][o.s.u.c.UpdateCenter] The plugin 'securityphpfrontend' version : 9.0.0.12669 has not been found on the update center.
2024.03.08 11:48:09 INFO  web[AY4FlAcFB/KA6OylAHYD][o.s.u.c.UpdateCenter] The plugin 'securitypythonfrontend' version : 9.0.0.12669 has not been found on the update center.
2024.03.08 11:48:09 INFO  web[AY4FlAcFB/KA6OylAHYD][o.s.u.c.UpdateCenter] The plugin 'sonarapex' version : 1.8.3.2219 has not been found on the update center.
2024.03.08 11:48:09 INFO  web[AY4FlAcFB/KA6OylAHYD][o.s.u.c.UpdateCenter] The plugin 'sonarscala' version : 1.8.3.2219 has not been found on the update center.
2024.03.08 11:48:09 INFO  web[AY4FlAcFB/KA6OylAHYD][o.s.u.c.UpdateCenter] The plugin 'swift' version : 4.3.1.4892 has not been found on the update center.
2024.03.08 11:48:09 INFO  web[AY4FlAcFB/KA6OylAHYD][o.s.u.c.UpdateCenter] The plugin 'tsql' version : 1.5.1.4340 has not been found on the update center.
2024.03.08 11:48:09 INFO  web[AY4FlAcFB/KA6OylAHYD][o.s.u.c.UpdateCenter] The plugin 'vb' version : 2.7.1.2721 has not been found on the update center.
2024.03.08 11:48:09 INFO  web[AY4FlAcFB/KA6OylAHYD][o.s.u.c.UpdateCenter] The plugin 'vbnet' version : 8.25.0.33663 has not been found on the update center.
2024.03.08 11:48:09 INFO  web[AY4FlAcFB/KA6OylAHYD][o.s.u.c.UpdateCenter] The plugin 'web' version : 3.4.0.2754 has not been found on the update center.
2024.03.08 11:48:09 INFO  web[AY4FlAcFB/KA6OylAHYD][o.s.u.c.UpdateCenter] The plugin 'xml' version : 2.2.0.2973 has not been found on the update center.
2024.03.08 18:28:28 INFO  web[][o.s.s.a.p.ExpiredSessionsCleaner] Purge of expired session tokens has removed 0 elements
2024.03.08 18:28:28 INFO  web[][o.s.s.a.p.ExpiredSessionsCleaner] Purge of expired SAML message ids has removed 0 elements
2024.03.09 18:28:28 INFO  web[][o.s.s.a.p.ExpiredSessionsCleaner] Purge of expired session tokens has removed 0 elements
2024.03.09 18:28:28 INFO  web[][o.s.s.a.p.ExpiredSessionsCleaner] Purge of expired SAML message ids has removed 0 elements
2024.03.10 18:28:28 INFO  web[][o.s.s.a.p.ExpiredSessionsCleaner] Purge of expired session tokens has removed 1 elements
2024.03.10 18:28:28 INFO  web[][o.s.s.a.p.ExpiredSessionsCleaner] Purge of expired SAML message ids has removed 0 elements

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

2

Hi,

Your version is past EOL. You should upgrade to either the latest version or the current LTA (long-term active version) at your earliest convenience. Your upgrade path is:

9.0 → 9.9.4 → 10.4 (last step optional)

You may find these resources helpful:

If you have questions about upgrading, feel free to open a new thread for that here.

If your error persists after upgrade, please come back to us. Make sure you also use the version of the helm chart compatible with your target version – 8.0.3 for 9.9.4, or the latest version for 10.4.

3

Hi Colin

Thanks for your suggestion.
Currently we are Migrating our Database from Postgres to MS Sql using SonarQube DB copy tool, Where we are creating a new similar instance which is targeting to new Sql Database. It is mentioned in the documentation that while migrating we need to use same SonarQube that matches the version and edition of your source instance.
Link: SonarQube database copy tool

Suggest me what is the best way to proceed further