Description of problem:
[Pre-Merge-Testing] OVN pods crashed after restarting when configuring NADs
build
Version-Release number of selected component (if applicable):
4.19,openshift/api#1997,openshift/ovn-kubernetes#2412

How reproducible:
Always

Steps to Reproduce:

1. Create a namespace

2. Create a valid NAD in the namespace, like

apiVersion: k8s.cni.cncf.io/v1
kind: NetworkAttachmentDefinition
metadata:
  name: l3-network-ns1
  namespace: ns1
spec:
  config: |2
    {
            "cniVersion": "0.3.1",
            "name": "l3-network-ns1",
            "type": "ovn-k8s-cni-overlay",
            "topology":"layer3",
            "subnets": "10.20.0.0/16/24",
            "mtu": 1300,
            "netAttachDefName": "ns1/l3-network-ns1",
            "role": "primary"
    }

3. Restart OVN pods

Actual results:

% oc get pods -n openshift-ovn-kubernetes
NAME                                     READY   STATUS             RESTARTS      AGE
ovnkube-control-plane-6989cdfc8d-nm96c   2/2     Running            0             2m50s
ovnkube-control-plane-6989cdfc8d-zsfr6   2/2     Running            0             2m51s
ovnkube-node-5ssv7                       7/8     CrashLoopBackOff   4 (67s ago)   2m49s
ovnkube-node-7mffw                       7/8     CrashLoopBackOff   4 (79s ago)   2m48s
ovnkube-node-dbhvt                       7/8     CrashLoopBackOff   4 (78s ago)   2m47s
ovnkube-node-j8mdj                       7/8     CrashLoopBackOff   4 (69s ago)   2m48s
ovnkube-node-nknpc                       7/8     CrashLoopBackOff   4 (65s ago)   2m47s
ovnkube-node-xnvdc                       7/8     CrashLoopBackOff   4 (60s ago)   2m47s

Expected results:
OVN pods runs smoothly.

Additional info:

Please fill in the following template while reporting a bug and provide as much relevant information as possible. Doing so will give us the best chance to find a prompt resolution.

Affected Platforms:

Is it an

1. internal CI failure
2. customer issue / SD
3. internal RedHat testing failure

If it is an internal RedHat testing failure:

• Please share a kubeconfig or creds to a live cluster for the assignee to debug/troubleshoot along with reproducer steps (specially if it's a telco use case like ICNI, secondary bridges or BM+kubevirt).

If it is a CI failure:

• Did it happen in different CI lanes? If so please provide links to multiple failures with the same error instance
• Did it happen in both sdn and ovn jobs? If so please provide links to multiple failures with the same error instance
• Did it happen in other platforms (e.g. aws, azure, gcp, baremetal etc) ? If so please provide links to multiple failures with the same error instance
• When did the failure start happening? Please provide the UTC timestamp of the networking outage window from a sample failure run
• If it's a connectivity issue,
• What is the srcNode, srcIP and srcNamespace and srcPodName?
• What is the dstNode, dstIP and dstNamespace and dstPodName?
• What is the traffic path? (examples: pod2pod? pod2external?, pod2svc? pod2Node? etc)

If it is a customer / SD issue:

• Provide enough information in the bug description that Engineering doesn’t need to read the entire case history.
• Don’t presume that Engineering has access to Salesforce.
• Do presume that Engineering will access attachments through supportshell.
• Describe what each relevant attachment is intended to demonstrate (failed pods, log errors, OVS issues, etc).
• Referring to the attached must-gather, sosreport or other attachment, please provide the following details:
  • If the issue is in a customer namespace then provide a namespace inspect.
  • If it is a connectivity issue:
    • What is the srcNode, srcNamespace, srcPodName and srcPodIP?
    • What is the dstNode, dstNamespace, dstPodName and dstPodIP?
    • What is the traffic path? (examples: pod2pod? pod2external?, pod2svc? pod2Node? etc)
    • Please provide the UTC timestamp networking outage window from must-gather
    • Please provide tcpdump pcaps taken during the outage filtered based on the above provided src/dst IPs
  • If it is not a connectivity issue:
    • Describe the steps taken so far to analyze the logs from networking components (cluster-network-operator, OVNK, SDN, openvswitch, ovs-configure etc) and the actual component where the issue was seen based on the attached must-gather. Please attach snippets of relevant logs around the window when problem has happened if any.

• When showing the results from commands, include the entire command in the output.  
• For OCPBUGS in which the issue has been identified, label with “sbr-triaged”
• For OCPBUGS in which the issue has not been identified and needs Engineering help for root cause, label with “sbr-untriaged”
• Do not set the priority, that is owned by Engineering and will be set when the bug is evaluated
• Note: bugs that do not meet these minimum standards will be closed with label “SDN-Jira-template”
• For guidance on using this template please see
  OCPBUGS Template Training for Networking  components