This bug was fixed in the package horizon - 2:9.1.2-0ubuntu5
---------------
horizon (2:9.1.2-0ubuntu5) xenial; urgency=medium
[ Seyeong Kim ]
* Hide unused consistency groups tab (LP: #1582725)
- d/p/hide-unused-consistency-groups.patch: Pick some policies from
upstream commit 388708b251b0487bb22fb3ebb8fcb36ee4ffdc4f to hide
unused consistency groups tab.
[ Corey Bryant ]
* d/openstack-dashboard.postinst: Ensure permissions are not
world-readable for /etc/openstack-dashboard/local_settings.py
(LP: #1755027).
[ Shane Peters ]
* d/p/let-nova-to-pick-availability-zone.patch:
In the Angular Launch Instance, if there is more than one
availability zone default to the option for the Nova scheduler to pick.
This is regression from the legacy Launch Instance feature (LP: #1613900).
-- Corey Bryant <corey.bry...@canonical.com> Thu, 15 Mar 2018 13:57:14
-0400
** Changed in: horizon (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
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:
Fix Released
Status in OpenStack Dashboard (Horizon):
Fix Released
Status in horizon package in Ubuntu:
Invalid
Status in horizon source package in Xenial:
Fix Released
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://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...
[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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1613900/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
