Bug 1318680

Summary:	[RFE] Terminating state does not give users details as to why pod is terminating or how.
Product:	OpenShift Container Platform	Reporter:	Eric Rich <erich>
Component:	RFE	Assignee:	Derek Carr <decarr>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Johnny Liu <jialiu>
Severity:	high	Docs Contact:
Priority:	medium
Version:	3.1.0	CC:	andcosta, aos-bugs, bbreard, byount, cscribne, decarr, emahoney, erich, jkaur, jokerman, jstakun, knakayam, mbarrett, misalunk, mmccomas, mtaru, myllynen, nicholas_schuetz, sakulkar, sjenning, tcarlin, tkatarki
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1318497	Environment:
Last Closed:	2019-04-22 18:38:51 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:
Bug Depends On:	1318497
Bug Blocks:

Description Eric Rich 2016-03-17 13:40:58 UTC

+++ This bug was initially created as a clone of Bug #1318497 +++

Description of problem:

-  There are no clue given in the "oc get event" command as to what is happening during the Terminating process. This should be improved.

Version-Release number of selected component (if applicable):

- v3.1.1.6

Actual results:


Expected results:



Additional info:

Comment 27 Eric Rich 2019-04-20 20:00:38 UTC

*** Bug 1542715 has been marked as a duplicate of this bug. ***

Comment 28 Tushar Katarki 2019-04-22 18:38:51 UTC

This RRE is addressed by https://kubernetes.io/docs/tasks/debug-application-cluster/determine-reason-pod-failure/ since OCP 3.9.