-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.17.z, 4.16.z, 4.18.z, 4.19.z, 4.20.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
CORENET Sprint 280
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem: The oc get eip command returns only a single EgressIP, even though multiple EgressIP addresses are specified in the EgressIP custom resource definition.
Version-Release number of selected component (if applicable): 4.18.27 but I reproduced this issue on multiple OCP versions including 4.20.1
How reproducible: - Create a EgressIP CR with multiple IP's:
Steps to Reproduce:
apiVersion: k8s.ovn.org/v1
kind: EgressIP
metadata:
annotations:
spec:
egressIPs:
- 10.x.xx.xx
- 10.x.xx.xx
namespaceSelector:
matchLabels:
name: abc
status:
items:
- egressIP: 10.x.xx.xx
node: worker-1.example.redhat.com
- egressIP: 10.x.xx.xx
node: worker-0.example.redhat.com
Check the egressip status with below command:
$ oc get eip
NAME EGRESSIPS ASSIGNED NODE ASSIGNED EGRESSIPS
egressip-43 10.x.xx.xx worker-1.example.redhat.com 10.x.xx.xx
Actual results: only one egressip is seen in oc get eip output.
Expected results: All the IP defined in EgressIP CR should be included in the oc get eip output.
$ oc get eip NAME EGRESSIPS ASSIGNED NODE ASSIGNED EGRESSIPS egressip-43 10.x.xx.xx worker-1.example.redhat.com 10.x.xx.xx 10.x.xx.xx
Additional info: Raised OCPBUS as per discussion in below slack thread:
https://redhat-internal.slack.com/archives/CDCP2LA9L/p1762946993950449
