Bug 2055551

Summary: Unable to create more than one egress IP per namespace
Product: OpenShift Container Platform Reporter: Patryk Diak <pdiak>
Component: NetworkingAssignee: Ben Bennett <bbennett>
Networking sub component: ovn-kubernetes QA Contact: Anurag saxena <anusaxen>
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: high    
Priority: high CC: anusaxen
Version: 4.10   
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2055549 Environment:
Last Closed: 2022-02-17 08:36:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2055549    

Description Patryk Diak 2022-02-17 08:35:38 UTC 
+++ This bug was initially created as a clone of Bug #2055549 +++

Description of problem:


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


How reproducible:
- Always


Steps to Reproduce:
1. Apply EIP similar to the following:
apiVersion: k8s.ovn.org/v1
kind: EgressIP
metadata:
  name: egressip-1
spec:
  egressIPs:
  - 172.18.0.33
  namespaceSelector:
    matchLabels:
      name: test
  podSelector:
    matchLabels:
      name: test-1
---

apiVersion: k8s.ovn.org/v1
kind: EgressIP
metadata:
  name: egressip-2
spec:
  egressIPs:
  - 172.18.0.44
  namespaceSelector:
    matchLabels:
      name: test
  podSelector:
    matchLabels:
      name: test-2

Actual results:
Only the first egress IP works

Expected results:
Both egressip-1 and egressip-2 should work