Bug 1707049

Summary:	no termination message provided by integrated-oauth-server pod
Product:	OpenShift Container Platform	Reporter:	Luis Sanchez <sanchezl>
Component:	apiserver-auth	Assignee:	Mo <mkhan>
Status:	CLOSED ERRATA	QA Contact:	Chuan Yu <chuyu>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	aos-bugs, mkhan
Target Milestone:	---
Target Release:	4.1.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-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:09:24 UTC

The integrated-oauth-server 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

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

Comment 2 Mo 2019-05-06 22:20:54 UTC

https://github.com/openshift/cluster-authentication-operator/pull/127

Comment 4 Chuan Yu 2019-05-07 06:47:16 UTC

Verified on 4.1.0-0.nightly-2019-05-06-234425

$ oc get po oauth-openshift-f -o json | jq '.spec.containers[].terminationMessagePolicy'
"FallbackToLogsOnError"

Comment 6 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