unhealthy juju-db is invisible
Bug #1806760 reported by
Paul Collins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
I just discovered that the mongodb replicaset of one of our Juju controllers was unhealthy as I was preparing for an upgrade, because juju create-backup was attempted on a secondary (this is a bug in itself, LP:1790875, but it was helpful here) that was in RECOVERING state.
mongodb is a critical wad of dark matter underpinning Juju that we have to deal with directly in order to monitor and manage. Juju should at least have some way of making the operator aware of an unhealthy database so that they can start Googling feverishly for help on fixing it.
Revision history for this message
| Richard Harding (rharding) wrote | #1 |
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| milestone: | none → 2.6-beta1 |
| Changed in juju: | |
| milestone: | 2.6-beta1 → 2.6-beta2 |
| Changed in juju: | |
| milestone: | 2.6-beta2 → 2.6-rc1 |
| Changed in juju: | |
| milestone: | 2.6-rc1 → 2.6-rc2 |
| Changed in juju: | |
| milestone: | 2.6-rc2 → 2.6.1 |
| Changed in juju: | |
| milestone: | 2.6.1 → 2.6.2 |
| Changed in juju: | |
| milestone: | 2.6.2 → 2.6.3 |
| Changed in juju: | |
| milestone: | 2.6.3 → 2.6.4 |
| Changed in juju: | |
| milestone: | 2.6.4 → 2.6.5 |
| Changed in juju: | |
| milestone: | 2.6.5 → 2.6.6 |
| Changed in juju: | |
| milestone: | 2.6.6 → 2.6.7 |
| Changed in juju: | |
| milestone: | 2.6.7 → 2.7-beta1 |
| Changed in juju: | |
| milestone: | 2.7-beta1 → 2.7-rc1 |
| Changed in juju: | |
| milestone: | 2.7-rc1 → none |
| tags: | added: health-check |
Revision history for this message
| Peter De Sousa (pjds) wrote | #2 |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #3 |
| Changed in juju: | |
| importance: | Medium → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
Thank you. This falls directly into the work we want to do around an easy to consume health report for Juju controllers, in particular around HA status and mongo status.