Description of problem: SDN-561(Multus Default route overwrite) passed on SDN but failed on OVN Version-Release number of selected component (if applicable): 4.5.0-0.nightly-2020-04-28-084038 How reproducible: Always Steps to Reproduce: 1.Create NetworkAttachmentDefinition curl -s https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/networking/multus-cni/NetworkAttachmentDefinitions/ipam-static.yaml | sed s/ipam-name/bridge-static/g | sed s/ipam-type/bridge/g | oc create -f- 2.Create a pod oc create -f https://raw.githubusercontent.com/weliang1/Openshift_Networking/master/Features/multus/multus-default-route-pod.yaml 3.oc describe pod multus-default-route-pod Warning FailedCreatePodSandBox 58m kubelet, ip-10-0-56-92.us-east-2.compute.internal Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_multus-default-route-pod_aff5m_f9bbe55a-be2d-425a-9530-033cf6abaedd_0(773e792c4123393bc625148235d18f4f8a1d6efafff6f5f9bca8e082961e6e13): Multus: [aff5m/multus-default-route-pod]: error adding container to network "ovn-kubernetes": delegateAdd: error invoking confAdd - "ovn-k8s-cni-overlay": error in getting result from AddNetwork: CNI request failed with status 400: '[aff5m/multus-default-route-pod] failed to configure pod interface: failed to add gateway route: one of Dst.IP, Src, or Gw must not be nil Actual results: Can not deploy multus pod Expected results: Can deploy multus pod Additional info: Same issue also happen in v4.4
Tested and verified in 4.5.0-0.nightly-2020-05-07-110323 [weliang@weliang ~]$ oc get pods NAME READY STATUS RESTARTS AGE multus-default-route-pod 1/1 Running 0 75s [weliang@weliang ~]$ oc exec multus-default-route-pod -- ip route default via 22.2.2.254 dev net1 10.128.0.0/14 via 10.128.2.1 dev eth0 10.128.2.0/23 dev eth0 proto kernel scope link src 10.128.2.13 22.2.2.0/24 dev net1 proto kernel scope link src 22.2.2.22 172.30.0.0/16 via 10.128.2.1 dev eth0 [weliang@weliang ~]$
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, 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-2020:2409