Bug 2088268

Summary: [Test-only] Octavia Availability zone feature, not yet supported
Product: Red Hat OpenStack Reporter: Donghwi Cha <dcha>
Component: openstack-octaviaAssignee: Nate Johnston <njohnston>
Status: NEW --- QA Contact: Bruna Bonguardo <bbonguar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 17.0 (Wallaby)CC: bbonguar, gthiemon, lpeer, majopela, njohnston, oschwart, scohen, youngkim
Target Milestone: ---Keywords: FutureFeature, TestOnly
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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:

Description Donghwi Cha 2022-05-19 06:06:17 UTC 
Description of problem:

Octavia Availability zone is fully working without any issue with the default openstack architecture where there is no edge and DCN, and spine leaf. 

But Octavia Availability zone is not yet supported by Red Hat


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


How reproducible:


Steps to Reproduce:
1. Install RHOSP 16.2.x with Octavia when deploying overcloud with the default architecture (without dcn or spine leaf)
2. create AZ and Host aggregation on Nova and use the AZ on CONF.nova.availability_zone in octavia.conf 
3. restart octavia worker container on controller  
4. deploy at least 4 computes, 3 for octavia, and 1 or more for additional compute host for testing 
5. test Active standby Octavia/Amphora LB of creation, and failover 
6. confirm that there is no issue and Amphora LB always successfully scheduled on AZ configured on octavia.conf 

Actual results:
AZ configuration is fully working without any issue 

Expected results:
AZ configuration is fully working without any issue 

Additional info:

there is no bug or no issue, but only QA is missing for the support of the AZ configuration on Octavia
Comment 4 Donghwi Cha 2022-05-24 13:09:15 UTC 
Hi. This Bugzilla is different from https://bugzilla.redhat.com/show_bug.cgi?id=1813565

This Bugzilla is only related with  CONF.nova.availability_zone in octavia.conf  
but BZ 1813565 is only related with providing input of AZ. 


Please see the logic below

        try:
            network_ids = network_ids or []
            port_ids = port_ids or []
            nics = []
            if network_ids:
                nics.extend([{"net-id": net_id} for net_id in network_ids])
            if port_ids:
                nics.extend([{"port-id": port_id} for port_id in port_ids])

            server_group = None if server_group_id is None else {
                "group": server_group_id}
            az_name = availability_zone or CONF.nova.availability_zone     <-- it is either by input for each lb or by conf globally (CONF.nova.availability_zone)
            ...
            amphora = self.manager.create(
                name=name, image=image_id, flavor=amphora_flavor,
                block_device_mapping=block_device_mapping,
                key_name=key_name, security_groups=sec_groups,
                nics=nics,
                files=config_drive_files,
                userdata=user_data,
                config_drive=True,
                scheduler_hints=server_group,
                availability_zone=az_name
            )
Comment 5 Donghwi Cha 2022-05-24 13:35:03 UTC 
I've updated this BZ from Train to Wallaby since CONF.nova.availability_zone is still part of the new release, Wallaby,
and both of providing AZ for each LB creation and globally setting AZ to all LB still exist.