Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1417666

Summary:	Lack of Any availability zone in Horizon dashboard
Product:	Red Hat OpenStack	Reporter:	Francesco Vollero <fvollero>
Component:	python-django-horizon	Assignee:	Radomir Dopieralski <rdopiera>
Status:	CLOSED ERRATA	QA Contact:	Ido Ovadia <iovadia>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	9.0 (Mitaka)	CC:	aortega, athomas, beth.white, mfuruta, mrunge, srevivo
Target Milestone:	async	Keywords:	ZStream
Target Release:	9.0 (Mitaka)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	python-django-horizon-9.0.1-6.el7ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1426670 (view as bug list)		Environment:
Last Closed:	2017-03-08 17:46:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1426670

Description Francesco Vollero 2017-01-30 15:29:42 UTC

Description of problem:

Lack of the feature "Any availability zone" in Horizon dashboard when used to spawn new virtual machines into an environment with multiple Availability Zones.
There's a way to let Horizon let the Scheduler assign it to any AZ ?

Version-Release number of selected component (if applicable):

OSP9 - Mitaka

How reproducible:
Choosing an availability zone when creating an instance force you to choose an availability zone and not to let the scheduler pick it for you.

Actual results:
No option

Expected results:
To have "Any availability zone" 

Additional info:
Seems that got sorted out upstream, we could backport somehow ? 
https://bugs.launchpad.net/horizon/+bug/1613900

Comment 3 Radomir Dopieralski 2017-02-22 08:30:00 UTC

*** Bug 1421633 has been marked as a duplicate of this bug. ***

Comment 5 errata-xmlrpc 2017-03-08 17:46:59 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0466.html