-
Bug
-
Resolution: Done-Errata
-
Major
-
4.18
-
None
-
False
-
-
None
-
None
-
None
-
None
-
Rejected
-
CORENET Sprint 269
-
1
-
Done
-
Release Note Not Required
-
N/A
-
None
-
None
-
None
-
None
TLDR; There is a test which checks kubelet probes work well for UDN-enabled pods by ensuring the no. of pod restarts is 0 which means the startup/readiness/failure probes are all healthy.... unfortunately given rhel8 workers are using cgroupsv1 where UDNs are not supported, pod's will indeed be restarting and probes are expected to fail here.
So the test has to be modified to take into account whether this is an environment with cgroupsv1 or v2
however this is a test update bug, i can confirm there is no actual bug in the core code. This bug has been opened so that the tests can be fixed.
- depends on
-
OCPBUGS-53344 [4.19] Component Readiness: UDN isolation tests in origin are permafailing on nodes using cgroupsv1
-
- Closed
-
- is caused by
-
OCPBUGS-50513 ovnkube-controller container crashed on RHEL-8 worker
-
- Closed
-
- is cloned by
-
OCPBUGS-53344 [4.19] Component Readiness: UDN isolation tests in origin are permafailing on nodes using cgroupsv1
-
- Closed
-
- relates to
-
OCPBUGS-56937 workers-rhel8 jobs need ami update
-
- Verified
-
- links to
-
RHBA-2025:7863 OpenShift Container Platform 4.18.14 bug fix update