Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:

1. Install OCP 4.14.33 with SDN network on nutanix

2. Scale out worker node to 24 nodes and deploy infra/workload nodes

3. Upgrade OCP to 4.15.23, then upgrade to 4.16.4 on Nutanix

4. Execute limited OVN live migration using command 
oc patch Network.config.openshift.io cluster --type='merge' --patch '{"metadata":{"annotations":{"network.openshift.io/network-type-migration":""}},"spec":{"networkType":"OVNKubernetes"}}'
 
Actual results:

One of OVN Node Pod fail to created on Nutanix, we reproduce the issue twice, with the same error

 Warning  FailedCreatePodSandBox  72m                    kubelet            Failed to create pod sandbox: rpc error: code = Unknown desc = failed to mount container k8s_POD_ovnkube-node-qdl6k_openshift-ovn-kubernetes_660beece-892d-4946-a7e9-1a748e506077_0 in pod sandbox k8s_ovnkube-node-qdl6k_openshift-ovn-kubernetes_660beece-892d-4946-a7e9-1a748e506077_0(32cc6bd65bb52244171aac82bd2e5c8079aeba144eb382c57cdd882ed36fb487): creating overlay mount to /var/lib/containers/storage/overlay/09c8376f7315a7af7ac966c5ab5bf2deb6996e88543c605d40588993f762d6c8/merged, mount_data="lowerdir=/var/lib/containers/storage/overlay/l/UNJ75QLUPV7XMGYAL73SCVGLUF:/var/lib/containers/storage/overlay/l/MNN6WQNZ4AMYVNU4V3UOUBJ2OD:/var/lib/containers/storage/overlay/l/4OIRGLOAVXHL6MDV5BTP5LHOGT:/var/lib/containers/storage/overlay/l/ZI6D4EOMBPHLOBPQVHJPOJLUN5,upperdir=/var/lib/containers/storage/overlay/09c8376f7315a7af7ac966c5ab5bf2deb6996e88543c605d40588993f762d6c8/diff,workdir=/var/lib/containers/storage/overlay/09c8376f7315a7af7ac966c5ab5bf2deb6996e88543c605d40588993f762d6c8/work,volatile,context=\"system_u:object_r:container_file_t:s0:c279,c477\"": input/output error 

oc -n openshift-ovn-kubernetes get pods |grep Init
ovnkube-node-qdl6k                       0/8     Init:0/1   0          72m

Expected results:

All OVN Node Pod should created successfully. 

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