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.

Sign up for GitHub

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

Jump to bottom

Oncall Readyness status with sql connection down #4198

Open
gaetanars opened this issue Apr 10, 2024 · 0 comments
Open

Oncall Readyness status with sql connection down #4198

gaetanars opened this issue Apr 10, 2024 · 0 comments
Labels
bug Something isn't working more info needed needs triage

Comments

@gaetanars
Copy link

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?

  1. Launch Oncall-Engine pod
  2. 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
@gaetanars gaetanars added the bug Something isn't working label Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working more info needed needs triage
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@iskhakov @gaetanars