-
Bug
-
Resolution: Done
-
Normal
-
4.19.z, 4.20
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
x86_64
-
None
-
None
-
CNF Compute Sprint 274, CNF Compute Sprint 275, CNF Compute Sprint 276
-
3
-
Done
-
Release Note Not Required
-
N/A
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-59354. The following is the description of the original issue:
—
Description of problem:
E2E test to verify Guranteed pod is running after kubelet restart{ if the cpu manager state file is same after kubelet restart while we are verifying the above, we are not checking if Guranteed pod started before kubelet restart is also still running. code} Version-Release number of selected component (if applicable): {code:none}
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
This bug is created for backporting E2E test code and is not related to production
- clones
-
OCPBUGS-59354 E2E test to verify Guranteed pod is running after kubelet restart
-
- Verified
-
- is blocked by
-
OCPBUGS-59354 E2E test to verify Guranteed pod is running after kubelet restart
-
- Verified
-
- links to