fix: update default_availability_zones to a value (rackerlabs#528)

This change updates default_availability_zones to ensure it has a default value. While this option is supposed to assume the value of the bound az, openstack helm returns a `<no value>` value which makes the services very upset. By setting a value we make the service happy, and we all want happy services. Signed-off-by: Kevin Carter <[email protected]>
OpenStackKen · Nov 2, 2024 · 415dda8 · 415dda8
1 parent 40a146b
commit 415dda8
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/base-helm-configs/cinder/cinder-helm-overrides.yaml b/base-helm-configs/cinder/cinder-helm-overrides.yaml
@@ -759,7 +759,7 @@ conf:
   cinder:
     DEFAULT:
       storage_availability_zone: az1
-      default_availability_zone: null
+      default_availability_zone: az1
       allow_availability_zone_fallback: true
       scheduler_default_filters: AvailabilityZoneFilter,CapacityFilter,CapabilitiesFilter
       volume_usage_audit_period: hour

diff --git a/base-helm-configs/neutron/neutron-helm-overrides.yaml b/base-helm-configs/neutron/neutron-helm-overrides.yaml
@@ -1754,7 +1754,7 @@ conf:
       # NOTE(portdirect): the bind port should not be defined, and is manipulated
       # via the endpoints section.
       bind_port: null
-      default_availability_zones: null
+      default_availability_zones: az1
       network_scheduler_driver: neutron.scheduler.dhcp_agent_scheduler.AZAwareWeightScheduler
       router_scheduler_driver: neutron.scheduler.l3_agent_scheduler.AZLeastRoutersScheduler
       dhcp_load_type: networks