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

[Shane Peters]

Backport of patch to Mitaka for Ubuntu Cloud Archive.

** Patch added: "horizon_9.1.2-0ubuntu4.patch"
   https://bugs.launchpad.net/horizon/+bug/1613900/+attachment/5030577/+files/horizon_9.1.2-0ubuntu4.patch

** Changed in: horizon (Ubuntu)
     Assignee: (unassigned) => Shane Peters (shaner)

** Changed in: horizon (Ubuntu)
       Status: New => In Progress

** Changed in: horizon (Ubuntu)
    Milestone: None => xenial-updates

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
https://bugs.launchpad.net/bugs/1613900

Title:
  Unable to use 'Any' availability zone when spawning instance

Status in Ubuntu Cloud Archive:
  In Progress
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  In Progress

Bug description:
  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...

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1613900/+subscriptions