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?
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
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.
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
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.
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 ?
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.