Description of problem: Duplicate EgressIP getting assigned to nodes.

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

How reproducible:

Created duplicate EgressIP egress-group1 and egressdec with IP (10.74.235.42) even-though it is not getting assigned to node.

oc get eip
NAME            EGRESSIPS      ASSIGNED NODE               ASSIGNED EGRESSIPS
egress-group1   10.74.235.42   master1.ocp4.klakhwar.com   10.74.235.42  --> Same IP (10.74.235.42)
egress-groupd   10.74.235.43   worker0.ocp4.klakhwar.com   10.74.235.43
egress-groupk   10.78.235.43                                
egressdec       10.74.235.42                                             ---> Same IP (10.74.235.42)
egressnov       10.74.235.46   worker0.ocp4.klakhwar.com   10.74.235.47 

Restarted OVN-controller pod duplicate EgressIP got assigned to nodes:

oc delete po ovnkube-control-plane-c889ffcfd-p2mnz
pod "ovnkube-control-plane-c889ffcfd-p2mnz" deleted
 
oc get po
NAME                                    READY   STATUS    RESTARTS   AGE
ovnkube-control-plane-c889ffcfd-2mvsg   2/2     Running   0          4s
ovnkube-control-plane-c889ffcfd-jp9lg   2/2     Running   0          38s
ovnkube-node-4j7p2                      8/8     Running   0          3d8h
ovnkube-node-7z56g                      8/8     Running   0          65s
ovnkube-node-9cp5n                      8/8     Running   0          3d8h
ovnkube-node-cgkrs                      8/8     Running   0          3d8h
ovnkube-node-p68lf                      8/8     Running   0          3d8h

oc get eip
NAME            EGRESSIPS      ASSIGNED NODE               ASSIGNED EGRESSIPS
egress-group1   10.74.235.42   master1.ocp4.klakhwar.com   10.74.235.42
egress-groupd   10.74.235.43   worker0.ocp4.klakhwar.com   10.74.235.43
egress-groupk   10.78.235.43                               
egressdec       10.74.235.42   master0.ocp4.klakhwar.com   10.74.235.42 

Steps to Reproduce:

As mentioned above.

Actual results: Duplicate EgressIP got assigned to node.

Expected results: Duplicate EgressIP should not get assigned.

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   Customer Issue.

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