-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.17.z, 4.16.z, 4.18.z, 4.19.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
CORENET Sprint 278, CORENET Sprint 279
-
2
-
In Progress
-
Bug Fix
-
-
None
-
None
-
None
-
None
Description of problem:
EgressFirewalls still retain information about each deleted machine. On large clusters this build up overtime and end up filling etcd / breaking the api server etc.
Version-Release number of selected component (if applicable):
reproducing with 4.19.10
How reproducible:
trivial:
Steps to Reproduce:
1. create an EgressFirewall
2. delete some machines
3. oc get egressfirewall default -o yaml --show-managed-fields
Actual results:
managedFields still contains fields
- apiVersion: k8s.ovn.org/v1
fieldsType: FieldsV1
fieldsV1:
f:status: {}
manager: worker-7j7fv
operation: Apply
subresource: status
time: "2025-09-25T21:57:58Z"
Expected results:
no leaked managed field
Additional info:
Please fill in the following template while reporting a bug and provide as much relevant information as possible. Doing so will give us the best chance to find a prompt resolution.
Affected Platforms:
OpenShift 4.16, 4.19
customer issue
- is cloned by
-
OCPBUGS-65514 deleted nodes still present in egressfirewalls managed fields
-
- New
-
- is depended on by
-
OCPBUGS-65514 deleted nodes still present in egressfirewalls managed fields
-
- New
-
- links to