Bug 1170242

Summary:	Inconsistent info of availability zone (az) if the default az is replaced
Product:	Red Hat OpenStack	Reporter:	Martin Schuppert <mschuppe>
Component:	openstack-nova	Assignee:	Sylvain Bauza <sbauza>
Status:	CLOSED ERRATA	QA Contact:	nlevinki <nlevinki>
Severity:	medium	Docs Contact:
Priority:	high
Version:	5.0 (RHEL 6)	CC:	berrange, dasmith, eglynn, jshortt, mschuppe, ndipanov, nlevinki, pablo.iranzo, pbrady, pcaruana, pchriste, sbauza, sferdjao, sgordon, slong, vromanso, yeylon
Target Milestone:	z3	Keywords:	Triaged, ZStream
Target Release:	6.0 (Juno)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	openstack-nova-2014.2.3-6.el7ost	Doc Type:	Bug Fix
Doc Text:	Previously, the availability-zone (AZ) information for an instance could be inconsistent when calling 'nova list' if the default zone had been replaced by another one. This meant that when calling 'nova show <inst_uuid>', the AZ information could switch intermittently between the default AZ and the host AZ. With this update, the AZ cache information is invalidated if the instance AZ is different from the cached AZ. As a result, the output for 'nova show <uuid>' is now consistent for AZ information.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-05-05 13:30:02 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:	743661, 1214764

Description Martin Schuppert 2014-12-03 14:54:18 UTC

Description of problem:

Reference - upstream bug :

https://bugs.launchpad.net/nova/+bug/1390033

Description:
On a single-node deployment of OpenStack (using DevStack), if the default availability zone of Nova is replaced by another one, then the API api.nova.server_list returns the list of VMs in which the info of availability zone is inconsistent. This results in the toggling effect of Horizon dashboard when displaying the list of instances (under tab "Project/Instances"). The toggling effect is caused by inconsistent info of availability zone whose values either the default one or the newly-created one.

Version-Release number of selected component (if applicable):
openstack-nova-2014.1.3-9.el7ost

How reproducible:
- Go to tab "Admin/Host Aggregates" to create a new host aggregate which is assigned with the current host. Pls note that if this newly-created host aggregate is not assigned with any host, then the availability zone won't be defined.
- After that, also under this view, we find (in the Availability zones) that the newly-created availability zone hides away the default one.
- Go to tab "System information"->"Compute Service", we find that nova-compute service is running in the newly-created availability zone while all the cinder services are running in the default availability zone.
- Go to tab "Project/Image" to select some image for creating a new bootable volume.
- This newly-created volume is then used to launch a new VM
- After launching a new VM, it's auto re-directed to the view of "Instances". At here, we can observe the toggling effect on the availability zone info. The instance get created in the default zone.

Comment 3 Stephen Gordon 2015-01-15 16:09:04 UTC

Assigning to Sylvain as he has been reviewing the upstream change.

Comment 11 nlevinki 2015-04-13 11:57:51 UTC

I need develop to add the fix, I will test it for A3 if the package is in.

Comment 15 nlevinki 2015-04-27 06:18:16 UTC

1) create a new Host Aggregates at Admin--> Host Aggregates
2) create an image at Project--> Images
3) create an instance with the new image and check it is active and in the new AZ
all tests are passed

Comment 17 errata-xmlrpc 2015-05-05 13:30:02 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-2015-0931.html