OpenStack provider doesn't try another AZ if the scheduler fails to find a valid host
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Heather Lanigan | ||
juju-core |
Won't Fix
|
High
|
Unassigned | ||
1.25 |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Juju's OpenStack provider doesn't fall back to an alternate AZ if an instance in the picked AZ fails to find a host to start on.
In my case, my development tenant isn't allowed to start instances in one of the two AZs. Juju tries to distribute a unit onto the bad AZ, the instance gets created successfully, but is then quickly set to ERROR when nova-scheduler fails to find any valid hosts. There's no way to deploy services in this environment without a manual "juju add-machine zone=foo" and "juju deploy bar --to 1234".
The provider is OpenStack (icehouse from trusty-updates) and my client is juju-core 1.21.3-
Console transcript: http://
machine-0.log: http://
environments.yaml: http://
Changed in juju-core: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 1.23 |
Changed in juju-core: | |
milestone: | 1.23 → none |
importance: | High → Medium |
tags: | added: openstack-provider |
Changed in juju-core: | |
importance: | Medium → High |
tags: | added: canonical-is |
Changed in juju-core: | |
milestone: | none → 2.0.0 |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0.0 → none |
milestone: | none → 2.0.0 |
Changed in juju-core: | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in juju-core: | |
status: | Triaged → Won't Fix |
Changed in juju: | |
milestone: | 2.0.0 → 2.0.1 |
Changed in juju: | |
milestone: | 2.0.1 → none |
Changed in juju: | |
milestone: | none → 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: | |
status: | Triaged → Incomplete |
milestone: | 2.2-beta3 → none |
Changed in juju: | |
status: | Fix Committed → Fix Released |
(Ignore the fact that both the good and the bad instances appear to be in the "nova" AZ. juju-bootstack- ci-machine- 1 is in "production", but an OpenStack bug causes instances with scheduler failures to show up in the default AZ.)