Openstack provider error not surfaced on bootstrap: AZ
Bug #1649990 reported by
Martin Packman
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
Medium
|
Heather Lanigan | ||
Bug Description
When bootstrapping on the datacenterd openstack cloud, if the machine is requested in the wrong avaiability zone, Juju creates the instance but then aborts with a cryptic error:
17:30:46 ERROR cmd supercommand.go:458 failed to bootstrap model: refreshing addresses: instances not found
What this really means is the instance is in ERROR state, and sing `nova show $INSTANCE_UUID` gives a useful message:
{"message": "No valid host was found. There are not enough hosts available.", "code": 500, "created": "2016-12-
The correct thing to do is bootstrap with an availability zone specified in a placement directive, `--to zone=$USABLE_ZONE` but this is not clear from the output juju provides.
| summary: |
- Openstack provider error not surfaced on bootstrap + Openstack provider error not surfaced on bootstrap: AZ |
| Changed in juju: | |
| importance: | High → Medium |
| milestone: | 2.2.0-beta2 → none |
Revision history for this message
| Heather Lanigan (hmlanigan) wrote | #1 |
| Changed in juju: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Heather Lanigan (hmlanigan) |
| milestone: | none → 2.2-beta4 |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This PR will try another availability zone and improve the error messaging.
https:/