Bug 1707065 - no termination message provided by failing cluster-autoscaler-operator pod
Summary: no termination message provided by failing cluster-autoscaler-operator pod
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 4.2.0
Assignee: Alberto
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-06 17:42 UTC by Luis Sanchez
Modified: 2019-10-16 06:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-16 06:28:30 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-autoscaler-operator pull 115 0 'None' closed Bug 1707065: Add terminationMessagePolicy to the CAO container 2020-05-26 05:30:12 UTC
Red Hat Product Errata RHBA-2019:2922 0 None None None 2019-10-16 06:28:47 UTC

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
Note You need to log in before you can comment on or make changes to this bug.