-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.12
-
+
-
No
-
False
-
-
-
Bug Fix
-
Done
This is a clone of issue OCPBUGS-32426. The following is the description of the original issue:
—
on clusters with a large number of services with externalIPs or services from type loadBalancer the ovnkube-node initialization can take up to 50 min
The problem is after a node reboot done by MCO the unschedule taint is removed from the node so the api allocates pods to that node that get stuck on ContrainerCreating and other nodes continue to go down for reboot making the workloads unavailable. (if no PDB exists for the workload to protect it)
- clones
-
OCPBUGS-32426 [4.15z] slow ovnkube-node initialization on large number of services with externalIps
- Closed
- is blocked by
-
OCPBUGS-32426 [4.15z] slow ovnkube-node initialization on large number of services with externalIps
- Closed
- is cloned by
-
OCPBUGS-33730 [4.13z] slow ovnkube-node initialization on large number of services with externalIps
- Closed
- is depended on by
-
OCPBUGS-33730 [4.13z] slow ovnkube-node initialization on large number of services with externalIps
- Closed
- links to
-
RHBA-2024:3331 OpenShift Container Platform 4.14.z bug fix update