-
Notifications
You must be signed in to change notification settings - Fork 133
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
[Bug] - Readiness probe fails, database driver unknown #404
Comments
Hi @ondrejbilcik, From the info you have supplied I cannot see anything immediately obvious that would cause this. For some more detail would it be possible to supply the configured |
@ondrejbilcik also a more detailed log will help, I wonder if jdbc url is picked up. |
Yes this was my thought too, is it possible the url is malformed. |
Hi, |
@ondrejbilcik thanks for sharing the files. What I noticed in the logs is:
This is how Jira entrypoint works - if the dbconfig.xml exists, it's not overwritten. Perhaps, you passed some malformed value the first time you installed the Helm chart? I'd suggest delete helm release, make sure PVCs are deleted as well. OR you can exec into jira container and remove @errcode1202 may have more info on whether or not overwriting dbconfig.xml is possible in the latest versions - we did have a discussion around that recently. |
@bianchi2 removing the file and killing the pod worked. Thanks a bunch. |
@ondrejbilcik awesome! Yes, currently, if you install the chart and pass malformed db related values, dbconfig.xml is messed and not overwritten when you run helm upgrade. This will be fixed as far as I know. |
Suggestion
Hi,
I'm running into some issues deploying the chart and would appreciate some pointers for troubleshooting.
My readiness probes are failing, with logs containing the following
I haven't been able to figure out why the database registers as Unknown, the config and the resulting env vars should be correct.
Thanks in advance
Product
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: