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

[Epic]: RHOSO 18 - bond interface does not work for control plane ovn gateway

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • rhos-18.0.15
    • None
    • ovn-operator
    • None
    • [Epic]: RHOSO 18 - bond interface does not work for control plane ovn gateway
    • Bug Tracking
    • False
    • Hide

      None

      Show
      None
    • False
    • Not Selected
    • ?
    • ?
    • Done
    • ?
    • rhos-connectivity-neutron
    • ?
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      .Bond interfaces can now be configured in RHOSO 18
      Before this update, bond interfaces configured in the `OpenStackControlPlane` custom resource (CR) for OVN gateways failed. The `ovn-operator` would throw an error similar to the following:
      [source,bash]
      ----
      …
      Path:"" ERRORED: error configuring pod [openstack/ovn-controller-ovs-5rjnm] networking: [openstack/ovn-controller-ovs-5rjnm/68204fb3-394d-4990-80d3-fc2e388c2ee3:datacentre]: error adding container to network "datacentre": failed to move link invalid argument
      ': StdinData:
      …
      ----
      With this update, the problem has been resolved, and the `ovn-operator` correctly creates bond interfaces on the `ovn-controller` and `ovn-controller-ovs` pods.
      Show
      .Bond interfaces can now be configured in RHOSO 18 Before this update, bond interfaces configured in the `OpenStackControlPlane` custom resource (CR) for OVN gateways failed. The `ovn-operator` would throw an error similar to the following: [source,bash] ---- … Path:"" ERRORED: error configuring pod [openstack/ovn-controller-ovs-5rjnm] networking: [openstack/ovn-controller-ovs-5rjnm/68204fb3-394d-4990-80d3-fc2e388c2ee3:datacentre]: error adding container to network "datacentre": failed to move link invalid argument ': StdinData: … ---- With this update, the problem has been resolved, and the `ovn-operator` correctly creates bond interfaces on the `ovn-controller` and `ovn-controller-ovs` pods.
    • Bug Fix
    • Done

      A bond interface for ovn gateway OpenStackControlPlane config does not work

      ovn:
      template:
      ovnController:
      networkAttachment: tenant
      nicMappings:
      datacentre: bond0

      Error for ovn-controller-ovs-* pod:

      Normal AddedInterface 2m44s (x66 over 17m) multus Add eth0 [10.128.0.35/23] from ovn-kubernetes
      Warning FailedCreatePodSandBox 2m43s (x57 over 15m) kubelet (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_ovn-controller-ovs-5rjnm_openstack_68204fb3-394d-4990-80d3-fc2e388c2ee3_0(4eddc6890d77f41256a473b0fc2337cca77bf370d22beebc55b55582bb82d059): error adding pod openstack_ovn-controller-ovs-5rjnm to CNI network "multus-cni-network": plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: 'ContainerID:"4eddc6890d77f41256a473b0fc2337cca77bf370d22beebc55b55582bb82d059" Netns:"/var/run/netns/28a94a1c-6cad-444e-9372-1ead721fa87b" IfName:"eth0" Args:"IgnoreUnknown=1;K8S_POD_NAMESPACE=openstack;K8S_POD_NAME=ovn-controller-ovs-5rjnm;K8S_POD_INFRA_CONTAINER_ID=4eddc6890d77f41256a473b0fc2337cca77bf370d22beebc55b55582bb82d059;K8S_POD_UID=68204fb3-394d-4990-80d3-fc2e388c2ee3" Path:"" ERRORED: error configuring pod [openstack/ovn-controller-ovs-5rjnm] networking: [openstack/ovn-controller-ovs-5rjnm/68204fb3-394d-4990-80d3-fc2e388c2ee3:datacentre]: error adding container to network "datacentre": failed to move link invalid argument
      ': StdinData:

      {"binDir":"/var/lib/cni/bin","clusterNetwork":"/host/run/multus/cni/net.d/10-ovn-kubernetes.conf","cniVersion":"0.3.1","daemonSocketDir":"/run/multus/socket","globalNamespaces":"default,openshift-multus,openshift-sriov-network-operator","logLevel":"verbose","logToStderr":true,"name":"multus-cni-network","namespaceIsolation":true,"type":"multus-shim"}

      Expected behavior
      bond interface work like individual interface

      Bug impact
      ovn gw config is limited to single interface for control plane

      Known workaround
      use single interface per bridge

      Additional context
      Doc: https://docs.redhat.com/en/documentation/red_hat_openstack_services_on_openshift/18.0/html-single/configuring_networking_services/index#ovn-gateway-ctrl-plane-dedicated-nic_configuring-gateways

              egarciar@redhat.com Elvira Garcia
              rhel-process-autobot RHEL Jira bot
              rhos-dfg-networking-squad-neutron
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated: