yahoo-eng-team team mailing list archive

[Corey Bryant <corey.bryant@xxxxxxxxxxxxx>]

** Also affects: cloud-archive/mitaka
   Importance: Undecided
       Status: New

** Also affects: horizon (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: cloud-archive/mitaka
       Status: New => Triaged

** Changed in: horizon (Ubuntu Xenial)
       Status: New => Triaged

** Changed in: cloud-archive/mitaka
   Importance: Undecided => High

** Changed in: horizon (Ubuntu Xenial)
   Importance: Undecided => High

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

** Changed in: cloud-archive
       Status: In Progress => Invalid

** Changed in: cloud-archive/mitaka
     Assignee: (unassigned) => Shane Peters (shaner)

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

** Changed in: cloud-archive/mitaka
     Assignee: Shane Peters (shaner) => (unassigned)

** Changed in: cloud-archive/mitaka
     Assignee: (unassigned) => Shane Peters (shaner)

** Changed in: cloud-archive
     Assignee: Shane Peters (shaner) => (unassigned)

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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1613900

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

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive mitaka series:
  Triaged
Status in OpenStack Dashboard (Horizon):
  Fix Released
Status in horizon package in Ubuntu:
  Invalid
Status in horizon source package in Xenial:
  Triaged

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