Oncall Readyness status with sql connection down
gaetanars opened this issue · 0 comments
gaetanars commented
What went wrong?
What happened:
- oncall-engine lost the database connection
django.db.utils.OperationalError: connection to server at "xxxxxxxx" (172.20.189.66), port 5432 failed: FATAL: Sorry, too many clients already
- Readyness probe continue to say that all is ok
- Kubernetes don't kill pod
What did you expect to happen:
- Readyness probe must be KO when database connection is down (or other vital connection)
How do we reproduce it?
- Launch Oncall-Engine pod
- Stop database or interrupt connection
Grafana OnCall Version
v1.3.112
Product Area
Other
Grafana OnCall Platform?
Kubernetes
User's Browser?
No response
Anything else to add?
No response