-
Bug
-
Resolution: Done
-
Major
-
None
-
4.12
-
Important
-
No
-
SDN Sprint 249
-
1
-
False
-
-
-
-
Workaround is to restart ovnkube-node pods; that fixed high memory utilization too
-
-
-
Description of problem:
egressIP isn't getting assigned on infra nodes & the OVN CNI logs indicate that the nodes aren't reachable. The object is created & nodes have *egress-assignable* label
Also, the infra nodes have Ingress router pods running & serving the traffic.
The node never went NotReady & is pingable which confirms the connectivity.
Version-Release number of selected component (if applicable):
OCP v4.12.33 using OVN-K
How reproducible:
occuring in customer environment
Steps to Reproduce:
1. Don't have a exact trigger for now 2. Might happen if we keep it running for longer on cluster 3.
Actual results:
EgressIP isn't getting assigned on the infra nodes
Expected results:
EgressIP should get assigned on node once label is present
Additional info:
Once a new infra node is added to cluster it gets the egressIP assigned. Faulty ones are still being shown as not reachable
