-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.19
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
Rejected
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
openshift-apiserver pods lack terminationmessagepolicy fallbacktologsonerror. This makes debugging in the field impossible when logs are unavailable.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
All management cluster pods should set terminationmessagepolicy to fallbacktologsonerror.
Additional info:
- blocks
-
OCPBUGS-56458 HCP pods not running with terminationmessagepolicyfallbacktologsonerror
-
- Closed
-
- is cloned by
-
OCPBUGS-56458 HCP pods not running with terminationmessagepolicyfallbacktologsonerror
-
- Closed
-
- is depended on by
-
OCPBUGS-56930 Component Readiness: [HyperShift] upgrade test regressed
-
- Closed
-
- is related to
-
OCPBUGS-56051 terminationMessagePolicy not set to FallbackToLogsOnError for CNO operands on HCP
-
- Verified
-
- links to