Bug 1766503

Summary: [OSP13] Include nova::availability_zone in nova::api and nova::conductor
Product: Red Hat OpenStack Reporter: Martin Schuppert <mschuppe>
Component: puppet-novaAssignee: Martin Schuppert <mschuppe>
Status: CLOSED ERRATA QA Contact: OSP DFG:Compute <osp-dfg-compute>
Severity: medium Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: jjoyce, jschluet, nlevinki, nova-maint, slinaber, tvignaud
Target Milestone: z11Keywords: Patch, Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-nova-12.5.0-3.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1766502 Environment:
Last Closed: 2020-03-10 11:22:02 UTC Type: ---
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: 1766494, 1766500, 1766502    
Bug Blocks:    

Description Martin Schuppert 2019-10-29 10:01:12 UTC 
+++ This bug was initially created as a clone of Bug #1766502 +++

+++ This bug was initially created as a clone of Bug #1766500 +++

+++ This bug was initially created as a clone of Bug #1766494 +++

Description of problem:

For some reason this was included in nova::compute and nova::scheduler
but never included in nova::api eventhough bug #1529065 specifically
calls out the fact that it is missing.

Looking at the code - nova-api definitely requires it.
E.g the server create request handler sets the target AZ to
CONF.default_schedule_zone if none
https://github.com/openstack/nova/blob/stable/queens/nova/api/openstack/compute/servers.py#L486

and the az request handler skips the internal_service_availabily_zone
when listing AZs
https://github.com/openstack/nova/blob/stable/queens/nova/api/openstack/compute/availability_zone.py#L38

nova-conductor also requires it as it calls
availability_zones.get_host_availability_zone which defaults to
CONF.default_availability_zone
Comment 3 errata-xmlrpc 2020-03-10 11:22: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://access.redhat.com/errata/RHBA-2020:0760