app should differentiate between DBs being temporarily unavailable, and being marked as down by a human (via the /readonly interface)
Bug #1119510 reported by
Tom Haddon
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical SSO provider |
Invalid
|
High
|
Łukasz Czyżykowski | ||
Bug Description
Currently if the app is unable to connect to a DB it creates a file marking it as down. This is the same file that's created if an admin marks the backend as down in the /readonly UI. What this means is, the app won't try to reconnect to this DB until that file is removed. For temporary DB issues, the app should try to reconnect, but when an admin marks a DB as down, it shouldn't retry until it's been updated in the /readonly UI.
| tags: | added: canonical-webops-as |
| tags: | added: u1-notrack |
Revision history for this message
| Tom Haddon (mthaddon) wrote | #1 |
| Changed in canonical-identity-provider: | |
| status: | New → Confirmed |
| Changed in canonical-identity-provider: | |
| importance: | Undecided → High |
| assignee: | nobody → Łukasz Czyżykowski (lukasz-czyzykowski) |
Revision history for this message
| Tom Haddon (mthaddon) wrote | #7 |
Revision history for this message
| Ricardo Kirkner (ricardokirkner) wrote | #8 |
| Changed in canonical-identity-provider: | |
| status: | Confirmed → Invalid |
To post a comment you must log in.
We got bitten by this again per https:/