-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.14
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Informational
-
No
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
EgressIP which configured on secondary NIC didn't failover to available egress node when original egress node NotReady
Version-Release number of selected component (if applicable):
pre-merge testing
How reproducible:
Always
Steps to Reproduce:
1. Label two nodes as egress node oc get node worker-1 --show-labels NAME STATUS ROLES AGE VERSION LABELS worker-1 Ready worker 18h v1.27.3+e123787 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,k8s.ovn.org/egress-assignable=,kubernetes.io/arch=amd64,kubernetes.io/hostname=worker-1,kubernetes.io/os=linux,node-role.kubernetes.io/worker=,node.openshift.io/os_id=rhcos % oc get node worker-2 --show-labels NAME STATUS ROLES AGE VERSION LABELS worker-2 Ready worker 18h v1.27.3+e123787 beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,k8s.ovn.org/egress-assignable=,kubernetes.io/arch=amd64,kubernetes.io/hostname=worker-2,kubernetes.io/os=linux,node-role.kubernetes.io/worker=,node.openshift.io/os_id=rhcos 2. Created an egressIP object and the egressIP in secondary NIC subnet oc get egressip NAME EGRESSIPS ASSIGNED NODE ASSIGNED EGRESSIPS egressip2 172.22.0.100 worker-1 172.22.0.100 3. Reboot worker-1 4. Check egressIP object
Actual results:
Before worker-1 came to Reday, egressIP didn't failover to worker-2, just no egress node assigned and kept in below status for about 4 minutes until worker-1 Ready. % oc get egressip NAME EGRESSIPS ASSIGNED NODE ASSIGNED EGRESSIPS egressip2 172.22.0.100
Expected results:
egressIP should failover to other available egress node
Additional info: