[Bug 1613900] [NEW] Unable to use 'Any' availability zone when spawning instance

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

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://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/instances/workflows/create_instance.py#L390

The JS implementation miss the logic if number of AZs is >1
https://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/project/static/dashboard/project/workflow/launch-instance/launch-instance-model.service.js#L321

Also, JS implementation looks ugly if you have lot of subnets per
network...

** Affects: cloud-archive
     Importance: Undecided
     Assignee: Shane Peters (shaner)
         Status: In Progress

** Affects: horizon
     Importance: High
     Assignee: Matt Borland (palecrow)
         Status: Fix Released

** Affects: horizon (Ubuntu)
     Importance: Undecided
     Assignee: Shane Peters (shaner)
         Status: In Progress


** Tags: angularjs newton-backport-potential patch
-- 
Unable to use 'Any' availability zone when spawning instance 
https://bugs.launchpad.net/bugs/1613900
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.