-
Bug
-
Resolution: Unresolved
-
Normal
-
4.19
-
None
-
None
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
Description of problem:
In one of the customer's issue, the crictl cmd always timeout to execute, so we need to extend the timeout value of the crictl cmd to mitigate this effect.
Version-Release number of selected component (if applicable):
How reproducible:
The customer issue. A high-load cluster probably helps to reproduce this problem.
Steps to Reproduce:
The customer issue. A high-load cluster probably helps to reproduce this problem.
Actual results:
N/A
Expected results:
The crictl cmd should use a larger value as its timeout.
Additional info:
- blocks
-
OCPBUGS-76963 [release-4.18] Extend the timeout of crictl cmd
-
- New
-
- clones
-
OCPBUGS-76961 [release-4.20] Extend the timeout of crictl cmd
-
- New
-
- is blocked by
-
OCPBUGS-76961 [release-4.20] Extend the timeout of crictl cmd
-
- New
-
- is cloned by
-
OCPBUGS-76963 [release-4.18] Extend the timeout of crictl cmd
-
- New
-
- links to