Bug 1707066 - no termination message provided by failing cluster-monitoring-operator pod
Summary: no termination message provided by failing cluster-monitoring-operator pod
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Monitoring
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.1.0
Assignee: Sergiusz Urbaniak
QA Contact: Junqi Zhao
Depends On:
TreeView+ depends on / blocked
Reported: 2019-05-06 17:43 UTC by Luis Sanchez
Modified: 2019-06-04 10:48 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-06-04 10:48:31 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-monitoring-operator pull 347 0 None None None 2019-05-07 12:13:31 UTC
Red Hat Product Errata RHBA-2019:0758 0 None None None 2019-06-04 10:48:42 UTC

Description Luis Sanchez 2019-05-06 17:43:51 UTC
The cluster-monitoring-operator pod does not provide a termination message, hindering debugging efforts when the pods are crash looping.

At minimum, the pod's terminationMessagePolicy should be "FallbackToLogsOnError".

See https://kubernetes.io/docs/tasks/debug-application-cluster/determine-reason-pod-failure/#customizing-the-termination-message

Expected Results:
The termination message should appear in a pod container's  .status.lastState.terminated.message field.

Comment 2 Matthias Loibl 2019-05-07 12:19:54 UTC
A Pull Request with the fix has been made and it is about to be merged.

Comment 6 Junqi Zhao 2019-05-10 01:34:52 UTC
# oc -n openshift-monitoring get deploy cluster-monitoring-operator -oyaml | grep terminationMessagePolicy
        terminationMessagePolicy: FallbackToLogsOnError

payload: 4.1.0-0.nightly-2019-05-09-204138

Comment 8 errata-xmlrpc 2019-06-04 10:48:31 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.