Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1707065

Summary:	no termination message provided by failing cluster-autoscaler-operator pod
Product:	OpenShift Container Platform	Reporter:	Luis Sanchez <sanchezl>
Component:	Cloud Compute	Assignee:	Alberto <agarcial>
Status:	CLOSED ERRATA	QA Contact:	Jianwei Hou <jhou>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	agarcial, gblomqui, pthomas, zhsun
Target Milestone:	---
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-16 06:28:30 UTC	Type:	---
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:42:03 UTC

The cluster-autoscaler-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 1 Antonio Murdaca 2019-05-06 19:31:30 UTC

Not MCO...moving to Cloud

Comment 4 sunzhaohua 2019-08-09 07:59:49 UTC

Verified 

$ oc get pod cluster-autoscaler-operator-78b9b5fcf-l4vfc -o yaml
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: FallbackToLogsOnError

Comment 6 errata-xmlrpc 2019-10-16 06:28:30 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:2922