Unable to use 'Any' availability zone when spawning instance
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
High
|
Matt Borland | ||
Ubuntu Cloud Archive |
Invalid
|
Undecided
|
Unassigned | ||
Mitaka |
Fix Released
|
High
|
Shane Peters | ||
horizon (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
High
|
Shane Peters |
Bug Description
[Impact]
While using Mitaka, we found that by default, using js backend, it is not possible to choose 'any' availability zone. The issue is not fixed in master branch.
For python implementation the logic is:
https:/
The JS implementation miss the logic if number of AZs is >1
https:/
Also, JS implementation looks ugly if you have lot of subnets per network...
[Test Case]
Ensure that in the Angular Launch Instance, if there is more than one availability zone, it defaults to the option of Nova scheduler picking the AZ.
[Regression Potential]
Regression potential is fairly low. This bug has been fixed in all releases of OpenStack starting with Newton. The patch did have to be modified slightly to apply to mitaka.
Changed in horizon: | |
status: | New → Confirmed |
tags: | added: angularjs newton-backport-potential |
Changed in horizon: | |
milestone: | none → ocata-2 |
Changed in cloud-archive: | |
assignee: | nobody → Shane Peters (shaner) |
status: | New → In Progress |
Changed in horizon (Ubuntu Xenial): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in horizon (Ubuntu): | |
status: | In Progress → Invalid |
Changed in cloud-archive: | |
status: | In Progress → Invalid |
Changed in horizon (Ubuntu Xenial): | |
assignee: | nobody → Shane Peters (shaner) |
Changed in cloud-archive: | |
assignee: | Shane Peters (shaner) → nobody |
Changed in horizon (Ubuntu): | |
assignee: | Shane Peters (shaner) → nobody |
tags: | added: sts |
description: | updated |
tags: |
added: verification-done verification-done-xenial verification-mitaka-done removed: verification-mitaka-needed verification-needed verification-needed-xenial |
tags: |
added: verification-done verification-done-mitaka removed: verification-mitaka-needed verification-needed |
We've experienced this bug as well. Looking into it.