This is a clone of issue OCPBUGS-44303. The following is the description of the original issue:
—
Description of problem:

Network policy doesn't work properly during SDN live migration. During the migration, when the 2 CNI plugins are running in parallel. Cross-CNI traffic will be denied by ACLs generated for the network policy.

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

How reproducible:

Steps to reproduce:

1. Deploy a cluster with openshift-sdn

2. Create testpods in 2 different namespaces, z1 and z2.

3. In namespace z1, create a network policy that allows traffic from z2.

4. Trigger SDN live migration

5. Monitor the accessibility between the pods in Z1 and Z2.

Actual results:

When the pods in z1 and z2 on different nodes are using different CNI, the traffic is denied.

Expected results:

The traffic shall be allowed regardless of the CNI utilized by either pod.

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 (especially 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 are the srcNode, srcIP, srcNamespace and srcPodName?
• What are the dstNode, dstIP, 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, SOSR report, or other attachment, please provide the following details:
  • If the issue is in a customer namespace, then provide a namespace inspection.
  • If it is a connectivity issue:
    • What are the srcNode, srcNamespace, srcPodName and srcPodIP?
    • What are 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 have 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