Before this update, `openstack overcloud deploy` did not pass the value of the `OVNAvailabilityZone` role parameter to OVS.
+
With this update, the `OVNAvailabilityZone` role parameter correctly passes the value as an `availability-zones` value in `external-ids:ovn-cms-options`.
+
The following example shows how to use the parameter in an environment file to set `OVNAvailabilityZone. Include the environment file in the deployment command.
+
----
ControllerParameters:
OVNAvailabilityZone: 'az1'
----
+
The deployment adds `availability-zones=az1` to OVS `external-ids:ovn-cms-options`.
Description of problem:
On 17.0 with "OVNAvailabilityZone: '<availability_zone_value>'" on controller, the OVS configuration doesn't show up the configured values.
Version-Release number of selected component (if applicable):
Tried on 17.0 and OVNAvailabilityZone didn't seem to work.
How reproducible:
Always
Steps to Reproduce:
1. Create a overcloud environment file. Eg:
parameter_defaults:
NeutronDefaultAvailabilityZones: 'az-datacenter2,az-datacenter1'
ControllerParameters:
OVNCMSOptions: 'enable-chassis-as-gw'
OVNAvailabilityZone: 'az-datacenter2,az-datacenter1'
2. Trigger overcloud deployment with this environment file.
3. Check the ovn-cms-options in OVS external_ids using "ovs-vsctl get o . external_ids" in controller.
Actual results:
[root@controller-0 ~]# ovs-vsctl get o . external_ids
{hostname=controller-0.localdomain, ovn-bridge=br-int, ovn-bridge-mappings="datacentre:br-ex", ovn-chassis-mac-mappings="datacentre:fa:16:3e:d8:ae:ad", ovn-cms-options=enable-chassis-as-gw, ovn-encap-ip="172.16.4.76", ovn-encap-type=geneve, ovn-match-northd-version="true", ovn-monitor-all="true", ovn-openflow-probe-interval="60", ovn-remote="tcp:172.16.2.110:6642", ovn-remote-probe-interval="60000", rundir="/var/run/openvswitch", system-id="a8fb17f9-11d8-4eba-9efa-ebcb5fc3ea0d"}
Expected results:
Setting the parameter using "ovs-vsctl set Open_vSwitch . external-ids:ovn-cms-options="enable-chassis-as-gw,availability-zones=az-datacenter2:az-datacenter1" works.
[root@controller-0 ~]# ovs-vsctl get o . external_ids
{hostname=controller-0.localdomain, ovn-bridge=br-int, ovn-bridge-mappings="datacentre:br-ex", ovn-chassis-mac-mappings="datacentre:fa:16:3e:d8:ae:ad", ovn-cms-options=enable-chassis-as-gw,availability-zones=az-datacenter2:az-datacenter1, ovn-encap-ip="172.16.4.76", ovn-encap-type=geneve, ovn-match-northd-version="true", ovn-monitor-all="true", ovn-openflow-probe-interval="60", ovn-remote="tcp:172.16.2.110:6642", ovn-remote-probe-interval="60000", rundir="/var/run/openvswitch", system-id="a8fb17f9-11d8-4eba-9efa-ebcb5fc3ea0d"}
Additional info:
Referred this document: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.0/html/networking_guide/use-azs-make-network-nodes-ha_rhosp-network#config-network-service-azs-ovn_config_azs
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 (Red Hat OpenStack Platform 17.1.2 bug fix and enhancement 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-2024:0209
Description of problem: On 17.0 with "OVNAvailabilityZone: '<availability_zone_value>'" on controller, the OVS configuration doesn't show up the configured values. Version-Release number of selected component (if applicable): Tried on 17.0 and OVNAvailabilityZone didn't seem to work. How reproducible: Always Steps to Reproduce: 1. Create a overcloud environment file. Eg: parameter_defaults: NeutronDefaultAvailabilityZones: 'az-datacenter2,az-datacenter1' ControllerParameters: OVNCMSOptions: 'enable-chassis-as-gw' OVNAvailabilityZone: 'az-datacenter2,az-datacenter1' 2. Trigger overcloud deployment with this environment file. 3. Check the ovn-cms-options in OVS external_ids using "ovs-vsctl get o . external_ids" in controller. Actual results: [root@controller-0 ~]# ovs-vsctl get o . external_ids {hostname=controller-0.localdomain, ovn-bridge=br-int, ovn-bridge-mappings="datacentre:br-ex", ovn-chassis-mac-mappings="datacentre:fa:16:3e:d8:ae:ad", ovn-cms-options=enable-chassis-as-gw, ovn-encap-ip="172.16.4.76", ovn-encap-type=geneve, ovn-match-northd-version="true", ovn-monitor-all="true", ovn-openflow-probe-interval="60", ovn-remote="tcp:172.16.2.110:6642", ovn-remote-probe-interval="60000", rundir="/var/run/openvswitch", system-id="a8fb17f9-11d8-4eba-9efa-ebcb5fc3ea0d"} Expected results: Setting the parameter using "ovs-vsctl set Open_vSwitch . external-ids:ovn-cms-options="enable-chassis-as-gw,availability-zones=az-datacenter2:az-datacenter1" works. [root@controller-0 ~]# ovs-vsctl get o . external_ids {hostname=controller-0.localdomain, ovn-bridge=br-int, ovn-bridge-mappings="datacentre:br-ex", ovn-chassis-mac-mappings="datacentre:fa:16:3e:d8:ae:ad", ovn-cms-options=enable-chassis-as-gw,availability-zones=az-datacenter2:az-datacenter1, ovn-encap-ip="172.16.4.76", ovn-encap-type=geneve, ovn-match-northd-version="true", ovn-monitor-all="true", ovn-openflow-probe-interval="60", ovn-remote="tcp:172.16.2.110:6642", ovn-remote-probe-interval="60000", rundir="/var/run/openvswitch", system-id="a8fb17f9-11d8-4eba-9efa-ebcb5fc3ea0d"} Additional info: Referred this document: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.0/html/networking_guide/use-azs-make-network-nodes-ha_rhosp-network#config-network-service-azs-ovn_config_azs