MAAS storage constraint failure not reported in status
Bug #1642518 reported by
Michael Foord
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
If you deploy a charm (like prometheus) and specify storage, if the constraint can't be met (no machines with storage available) then the charm/machine stays in pending forever and the unmet constraint is not surfaced to the user in "juju status" - despite the error showing in the logs. (Tried with MAAS 2.)
The Prometheus charm supports storage so you can test with:
juju deploy cs:~prometheus-
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → 2.1-beta3 |
| Changed in juju: | |
| milestone: | 2.1-beta4 → 2.2.0 |
| Changed in juju: | |
| milestone: | 2.2-beta1 → 2.2-beta2 |
| Changed in juju: | |
| milestone: | 2.2-beta2 → 2.2-beta3 |
| Changed in juju: | |
| milestone: | 2.2-beta3 → 2.2-beta4 |
| Changed in juju: | |
| milestone: | 2.2-beta4 → 2.2-rc1 |
| tags: | added: constraints maas storage usability |
| Changed in juju: | |
| importance: | High → Medium |
| milestone: | 2.2-rc1 → none |
| tags: |
added: maas-provider removed: maas |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #1 |
| Changed in juju: | |
| importance: | Medium → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.