Bug 1707050

Summary:	no termination message provided by failing cluster-node-tuning-operator pod
Product:	OpenShift Container Platform	Reporter:	Luis Sanchez <sanchezl>
Component:	Node Tuning Operator	Assignee:	Jiří Mencák <jmencak>
Status:	CLOSED ERRATA	QA Contact:	Mike Fiedler <mifiedle>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	eparis, sejug
Target Milestone:	---
Target Release:	4.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:
Clones:	1707059 (view as bug list)		Environment:
Last Closed:	2019-06-04 10:48:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Luis Sanchez 2019-05-06 17:12:54 UTC

The cluster-node-tuning-operator pods do 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 1 Luis Sanchez 2019-05-06 17:14:56 UTC

Ditto for the tuned pod.

Comment 2 Jiří Mencák 2019-05-07 14:37:00 UTC

https://github.com/openshift/cluster-node-tuning-operator/pull/51

Comment 4 Jiří Mencák 2019-05-08 10:00:27 UTC

https://github.com/openshift/cluster-node-tuning-operator/pull/51 merged

Comment 6 Mike Fiedler 2019-05-15 17:05:49 UTC

Verified on:  4.1.0-0.nightly-2019-05-14-202907

# oc get deployment cluster-node-tuning-operator -o yaml | grep terminationMessagePolicy
        terminationMessagePolicy: FallbackToLogsOnError

Comment 8 errata-xmlrpc 2019-06-04 10:48:23 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.

https://access.redhat.com/errata/RHBA-2019:0758