-
Bug
-
Resolution: Done-Errata
-
Critical
-
None
-
4.14
-
None
-
Critical
-
No
-
SDN Sprint 238
-
1
-
Proposed
-
False
-
Description of problem:
non-ic aws environment, after run regression, found lots of egressIPs were not deleted from nodes
Version-Release number of selected component (if applicable):
4.14.0-0.ci-2023-06-20-200722 which includes the pr https://github.com/openshift/ovn-kubernetes/pull/1714
How reproducible:
Always
Steps to Reproduce:
1. After run regression cases, found lot's of egressIP were not cleared from node. Then reproduced manually. 2. Label one node as egress node, create on egressIP object % oc get egressip NAME EGRESSIPS ASSIGNED NODE ASSIGNED EGRESSIPS egressip-1 10.0.72.100 ip-10-0-72-134.us-east-2.compute.internal 10.0.72.100 3. Delete egressIP object % oc delete egressip --all egressip.k8s.ovn.org "egressip-1" deleted 4. Checking cloudprivateipconfig % oc get cloudprivateipconfig NAME AGE 10.0.48.183 53m 10.0.48.194 82m 10.0.48.54 85m 10.0.49.71 87m 10.0.49.95 60m 10.0.50.68 53m 10.0.50.87 91m 10.0.51.148 46m 10.0.51.174 47m 10.0.51.25 61m 10.0.54.53 72m 10.0.55.250 56m 10.0.56.177 47m 10.0.56.20 50m 10.0.58.199 80m 10.0.58.5 47m 10.0.60.121 48m 10.0.61.16 29m 10.0.61.180 89m 10.0.61.48 54m 10.0.62.64 54m 10.0.72.100 72s. ---The is left one in this manual test, others above are left by automation regression 3.
Actual results:
EgressIPs were not cleared from nodes after deleting egressIP objects
Expected results:
EgressIPs should be cleared from node
Additional info: