Helm deployment for sonar 8.5

[Brighty_Sara_Babu]

Must-share information (formatted with Markdown):

• which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
• what are you trying to achieve
• what have you tried so far to achieve this

Hi Guys,

Did anyine face issue with helm chart deployment of sonar with 8.5 version. If we are using external postgresql database it is saying unable to conmect to database. The setup works fine with 8.4. can you pls help me?

[OlivierK (Olivier Korach)]

Hello @Brighty_Sara_Babu,

Without a more detailed description of what you tried and what does not work we unfortunately can’t help.
Can you clarify the problem ?

Olivier

[Brighty_Sara_Babu]

We have pulled the helm chart from GitHub and deployed with azure managed postgresql with sonarqube version 8.3 and8.4. it works fine. But, whenc we try to do the same with sonarqube 8.5. it is not working. It is giving an error “failc to connect to the database”. , But if I use postgresql false and using the container database spun with the sonarqube It works fine. Let me know if you need more details

[OlivierK (Olivier Korach)]

Please send the details of how you deploy the SonarQube docker image (I am not and helm chart expert) add a zip of the SonarQube logs directory

[Brighty_Sara_Babu]

We are pulling the image from dockerhub using docker pull sonarqube:8.5.1-enterprise and deploying it using the command below.

Helm upgrade --install sonar stable/sonarqube --set postgresql.enabled=true --set database.type=postgresql --set postgresql.postgresqlserver=servername --set postgresql.postgresqlusername=username --set postgresql,postgresqlpasswors=password --set postgresql.postgresqldatabae=database --set image.tag=8.5.1-enterprise

[Brighty_Sara_Babu]

Attaching the error logs

[OlivierK (Olivier Korach)]

That helm command does not tell me anything because I don’t know how helm works (and this is not officially in the scope of what we support).
And a screenshot of the logs is no good for me. I need the full logs in text format.

[Brighty_Sara_Babu]

helm/charts

You can find more details of sonarqube deployment using helm here. The kubernetes deployment won’t comeup if there are any prestartup failures. So the only error in the log is fail to connect to database

[OlivierK (Olivier Korach)]

Sorry but here you are reversing the approach. You’re asking me to read helm documentation to be able to help you. This is something I cannot do. This is not supported at the moment.
I expect you to provide me what I ask you to be able to investigate.

[Brighty_Sara_Babu]

Do yo guys officially support kubernetes deployment?

[Brighty_Sara_Babu]

I have provided you all the logs I have and the way we deploy it. What else details you need from me?

[OlivierK (Olivier Korach)]

@OlivierK

And a screenshot of the logs is no good for me. I need the full logs in text format.

I hope my request is fair.

[Brighty_Sara_Babu]

Have attached the logs in text format

[OlivierK (Olivier Korach)]

Hello,

Thanks for the logs. There’s nothing obvious about why it’s not working (except that the postgres connection can’t be established). We should follow another track I think.
Now if you refer back to you reference to the helm chart you’re using you should notice some that hints that it’s not a reliable one. When one reads (OBSOLETE) as the first words of the description, this should raise an alarm, don’t you think ?

[ahaleiii (Alan Hale III)]

This might be related to the usage of Azure Database for PostgreSQL. There are a few other threads which suggest that gssEncMode is not currently supported by Azure Postgres and should be disabled, specifically around the upgrade to SonarQube 8.5.

SonarQube 8.5 released

SonarQube updated the postgres driver from 42.2.14 -> 42.2.16. Due changes on the default gssEncMode, this version and therefore SonarQube 8.5 is incompatible on Azure’s PostreSQL offering… a workaround is to add ?gssEncMode=disable to your connection string. maybe you would like to notify your users about that - or upgrade the driver to version xxxx.17 in the upcoming version. Cheers, Adrian see here too:

SQ 8.5 Docker image using Azure Postgressql

Hi @Jos_Wilbrink , we did some investigation and noticed that we upgraded the postgresql jdbc driver by 2 patch versions ( 42.2.14 to 42.2.16 ). and with that we dug deeper if there are any issues with this version connected to azure, and indeed there is one documented in the azure docs that hits what you observed perfectly! please try to disable GSS explicitly in the connect string, so like this: jdbc:postgresql://xxxxx.postgres.database.azure.com:5432/xxxx?gssEncMode=disable

SonarQube Upgrade 8.4 to 8.5 - Fail to connect to Azure PostgreSQL database

Hey, is your database hosted on Azure PostgreSQL PaaS? If yes, have a look here, there is a workaround to explicitly disable gssEncMode.

[Brighty_Sara_Babu]

Yeah thanks guys. Disabling gssencMode worked for 8.5 as well as 8.6. thanks a lot.

[Brighty_Sara_Babu]

Thanks Alan