-
Bug
-
Resolution: Done-Errata
-
Major
-
rhos-18.0 FR 1 (Nov 2024)
-
None
-
2
-
False
-
-
False
-
?
-
?
-
octavia-operator-container-1.0.5-3
-
?
-
?
-
None
-
-
Bug Fix
-
Done
-
-
-
Important
createDefaultLbMgmtNetwork and manageLbMgmtNetworks parameters have to be set to True by default, as described here:
https://github.com/openstack-k8s-operators/octavia-operator/blob/main/api/v1beta1/octavia_types.go
However, they are set to False when AZs are configured.
Example:
When this controlplane configuration is applied:
octavia: enabled: true template: amphoraImageContainerImage: registry-proxy.engineering.redhat.com/rh-osbs/rhoso18-octavia-amphora-image:18.0.1-2 apacheContainerImage: registry.redhat.io/ubi9/httpd-24:latest databaseInstance: openstack lbMgmtNetwork: availabilityZones: - zone-1 octaviaAPI: ...
The following octavia configuration is obtained:
$ oc -n openstack get octavia octavia -o jsonpath={.spec.lbMgmtNetwork} && echo {"availabilityZones":["zone-1"],"createDefaultLbMgmtNetwork":false,"manageLbMgmtNetworks":false}
The workaround is to set both createDefaultLbMgmtNetwork and manageLbMgmtNetworks to True within the controlplane CR.
- links to
-
RHBA-2025:144545 Release of containers for RHOSO OpenStack Podified images
- mentioned on