Bug 1501952

Summary:	Add controller state to oc adm diagnostics
Product:	OpenShift Container Platform	Reporter:	Matthew Robson <mrobson>
Component:	RFE	Assignee:	Derek Carr <decarr>
Status:	CLOSED WONTFIX	QA Contact:	Xiaoli Tian <xtian>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.6.1	CC:	aos-bugs, deads, jokerman, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-12 11:56:04 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 Matthew Robson 2017-10-13 14:53:24 UTC

Description of problem:

The only way to know if a specific controller was started and skipped is to have the initial start logs or to restart the controller.

It would be nice if oc adm diagnostics could tell us which are running / not running.

Ran into an issue where service-serving-cert was skipped due to a missing certificate, but those logs had rolled over. It was tough to determine why the service annotation 'service.alpha.openshift.io/serving-cert-secret-name: make-a-cert' was not working.

Ex:
Oct 12 10:23:27 atomic-openshift-master-controllers: I1012 10:23:27.804711   49015 start_master.go:773] Starting "openshift.io/service-serving-cert"
Oct 12 10:23:27 atomic-openshift-master-controllers: W1012 10:23:27.804716   49015 start_master.go:780] Skipping "openshift.io/service-serving-cert"

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

3.6.1

How reproducible:

Always

Actual results:

No way to debug if a controller is started or stopped

Expected results:

A way to better debug

Comment 2 David Eads 2017-10-13 16:14:29 UTC

Opened https://github.com/openshift/origin/pull/16863 to provide a warning in server start, controller start, and oc adm diagnostics.

Comment 4 Kirsten Newcomer 2019-06-12 11:56:04 UTC

With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers.  Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant.

This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. 

If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new 

Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new 

As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.