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

Bug 1397539

Summary:	[RFE] [Supportability] Pod diagnostics and data collection
Product:	OpenShift Container Platform	Reporter:	Eric Rich <erich>
Component:	RFE	Assignee:	Luke Meyer <lmeyer>
Status:	CLOSED WONTFIX	QA Contact:	Xiaoli Tian <xtian>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	aos-bugs, erich, jokerman, mmccomas, myllynen, tkatarki, wgordon
Target Milestone:	---
Target Release:	---
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-05-16 19:47:41 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:
Bug Depends On:	1397538
Bug Blocks:

Description Eric Rich 2016-11-22 18:28:53 UTC

+++ This bug was spun off of Bug #1207189#c5 +++

Description of problem:

Today the process for diagnosing issues with pods, is done in a hap-hazard fashion using a set of basic tools (https://docs.openshift.com/container-platform/3.3/cli_reference/basic_cli_operations.html#troubleshooting-and-debugging-cli-operations) to pull information out of a pod, or instrument it using tooling (that the pod has). 

This process needs to be better defined, so that customers of "Red Hat Supported" containers, have 1 defined way to collect/instrument a set of "well defined" logs or commands. 

------------

Ask: to have an 'oc command' or 'api endpoint' that create a "rhel/tools"(https://access.redhat.com/containers/#/repo/57ea8cf09c624c035f96f3bb) container, on the same node[s] as defined pod[s] and executes https://bugzilla.redhat.com/show_bug.cgi?id=1397538 against these pods.

Comment 4 Tushar Katarki 2019-05-16 19:47:41 UTC

Without knowing exactly what is expected, this RFE is not going anywhere. The scope of the RFE is very broad. If there are specific asks, lets have RFE requests for those specific asks instead of a uber RFE like this. 

And therefore this RFE has been open since OCP 3.3 !!!

Closing RFE.