Better error message when cloud resources aren't available
Bug #1620763 reported by
Antonio Rosales
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Expired
|
Medium
|
Unassigned | ||
Bug Description
In a recent Juju 2.0 Kubernetes demo we saw an issue where a new/default Google Cloud Platform user didn't have sufficient available resources to satisfy the bundle[0] constraints.
The issue we saw was the machine status stayed in "Pending" without notification the core problem was that the cloud could not fulfill the requested resource.
This bug is to request better error message(s) when a cloud cannot fulfill the requested resources instead of being stuck in "pending" or "error" in machine status during deploy.
| Changed in juju: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| tags: | added: usability |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → Expired |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.