Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-11092

createDefaultLbMgmtNetwork and manageLbMgmtNetworks set to False when AZs are defined

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • rhos-18.0.4
    • rhos-18.0 Feature Release 1 (Nov 2024)
    • octavia-operator
    • None
    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • ?
    • ?
    • ?
    • None
    • Hide
      .`createDefaultLbMgmtNetwork` and `manageLbMgmtNetworks` set to `false` when availability zones are defined

      When setting a list of availability zones in the Octavia CR (in `spec.lbMgmtNetwork.availabilityZones`), the default values of the `spec.lbMgmtNetwork.createDefaultLbMgmtNetwork` and `spec.lbMgmtNetwork.manageLbMgmtNetworks` settings are incorrectly reset to `false`.

      *Workaround:* When setting `availabilityZones` to a non-empty list in `spec.lbMgmtNetwork`, explicity set `createDefaultLbMgmtNetwork` and `manageLbMgmtNetworks to `true`.
      Show
      .`createDefaultLbMgmtNetwork` and `manageLbMgmtNetworks` set to `false` when availability zones are defined When setting a list of availability zones in the Octavia CR (in `spec.lbMgmtNetwork.availabilityZones`), the default values of the `spec.lbMgmtNetwork.createDefaultLbMgmtNetwork` and `spec.lbMgmtNetwork.manageLbMgmtNetworks` settings are incorrectly reset to `false`. *Workaround:* When setting `availabilityZones` to a non-empty list in `spec.lbMgmtNetwork`, explicity set `createDefaultLbMgmtNetwork` and `manageLbMgmtNetworks to `true`.
    • Known Issue
    • 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.

              rhn-support-gthiemon Gregory Thiemonge
              eolivare Eduardo Olivares Toledo
              rhos-dfg-networking-squad-vans
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: