-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.21.0
-
Quality / Stability / Reliability
-
False
-
-
5
-
Low
-
None
-
None
-
None
-
OCP Node Sprint 267 (Green), OCP Node Sprint 276 (green), OCP Node Sprint 277 (green), OCP Node Sprint 278 (green), OCP Node Sprint 279 (green)
-
5
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
in the fallout of https://github.com/openshift/machine-config-operator/pull/4765 which caused a CRI-O panic, TRT team needed to dig through node logs to find what process was failing. A test should catch a panic of CRI-O and Kubelet and report which node and process it happened on.
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1. create a segfault in kubelet or cri-o
Actual results:
sometimes the test may pass, if the node doesn't go NotReady
Expected results:
the tests should fail and catch this case
Additional info:
- is duplicated by
-
TRT-1927 Detect Panic In Kubelet Logs
-
- Closed
-
- links to