We’re using Sonar chart.
It seems our plugins sometimes deactivate themselves automatically when the pod restarts and they works again after the next restart.
Is that a known bug.
We’re using Sonarqube version 126.96.36.199424 and the chart version 3.0.0
Hi @Yanis_Corselle ,
Thanks for the report.
That’s weird, could you please share your custom values.yaml file or the properties that are overridden in the chart (make sure to anonymize the relevant values)
If you have the chance to reproduce it, please export and share the pod logs.
Try to check the log of container
install-plugins that is in charge of downloading the plugin:
kubectl logs sonarqube-sonarqube-0 install-plugins
You can also check the folder in the container of SonarQube once run:
kubectl exec -it sonarqube-sonarqube-0 -- bash
then check folders
/opt/sonarqube/extensions/plugins and list the files inside
Thanks for your answer.
The concerned part of the helmfile is this one :
plugins: install: - "https://github.com/elegoff/sonar-rust/releases/download/v0.0.9/community-rust-plugin-0.0.9.jar" - https://github.com/mc1arke/sonarqube-community-branch-plugin/releases/download/1.11.0/sonarqube-community-branch-plugin-1.11.0.jar lib: - sonarqube-community-branch-plugin-1.11.0.jar jvmOpts: "-javaagent:/opt/sonarqube/lib/common/sonarqube-community-branch-plugin-1.11.0.jar=web" jvmCeOpts: "-javaagent:/opt/sonarqube/lib/common/sonarqube-community-branch-plugin-1.11.0.jar=ce"
I can’t launch your commands because right now, it works again so the result would be useless.
Didn’t you ever face this problem ?
Apart from your previous post, we didn’t have any reports from other users, or experienced the same behavior in our internal instances.
I would be interested to know:
deploymentTypeyou are using
- if you set the
replicaCountother than 1
- if persistence is enabled (
Thanks for your answer.
We’re using the default values for these settings but our pods automatically restarts every day and then, sometimes the problem happen.
Maybe you could try to activate the persistence(
persistence.enabled). This will persist the application folders, and this may fix your problem since in that case, the plugin is already installed at startup.
Sorry I haven’t seen your answer …
The problem didn’t happen since the last time, if it happen again, we’ll try your fix. Thanks a lot !