Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SQ liveness probe missing #992

Closed
michaelsauter opened this issue Jun 28, 2021 · 5 comments · Fixed by #1267
Closed

SQ liveness probe missing #992

michaelsauter opened this issue Jun 28, 2021 · 5 comments · Fixed by #1267
Labels
documentation doc issues enhancement New feature or request

Comments

@michaelsauter
Copy link
Member

There is no livenessProbe configured for SonarQube, only a readiness probe. The liveness probe should depend on a working database connection, we have seen this to be broken.

Readiness probe is defined here: https://github.com/opendevstack/ods-core/blob/master/sonarqube/ocp-config/sonarqube.yml#L314-L323

@michaelsauter michaelsauter added the enhancement New feature or request label Jun 28, 2021
@gerardcl
Copy link
Member

hi @michaelsauter I will take a look into this for ODS 4.2.0

@gerardcl
Copy link
Member

thanks to @braisvq1996 to provide https://next.sonarqube.com/sonarqube/web_api <- will try to approach the fix via this API

@gerardcl
Copy link
Member

@michaelsauter FYI will try to close this issue via #1096

@gerardcl gerardcl added the documentation doc issues label Mar 15, 2022
@gerardcl
Copy link
Member

we will need to add a section in the admin docs that when upgrading sonarqube one needs to disable the probes

@BraisVQ
Copy link
Contributor

BraisVQ commented Aug 11, 2022

We can make use of this endpoint https://next.sonarqube.com/sonarqube/web_api/api/system/status as it does not need of any credential

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation doc issues enhancement New feature or request
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants