Bug 1769017

Summary:	Missing openapi CRD definitions for oc explain to work (controller-manager-operator)
Product:	OpenShift Container Platform	Reporter:	Maciej Szulik <maszulik>
Component:	Service Catalog	Assignee:	Joe Lanford <jlanford>
Status:	CLOSED ERRATA	QA Contact:	Fan Jia <jfan>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	jlanford
Target Milestone:	---
Target Release:	4.3.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:	2020-01-23 11:11:03 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 Maciej Szulik 2019-11-05 18:30:13 UTC

The following PR https://github.com/openshift/origin/pull/22696 introduced an e2e which is verifying that all the operators provide descriptive information as part of their schema which is then available through oc explain command. 
This was recently updated and brought back in https://github.com/openshift/origin/pull/24058. 

Your component has a few missing bits, see the commented out lines from the PR.

This should be fixed similarly to https://github.com/openshift/cluster-kube-controller-manager-operator/pull/302, 
iow. it should be using openshift/api's generated CRD yamls. 

Once done update origin's e2e test and uncomment the lines from your components.

Comment 2 Fan Jia 2019-11-08 07:03:36 UTC

test env:
cv:4.3.0-0.nightly-2019-11-07-172437

test result:
oc explain servicecatalogcontrollermanagers
KIND:     ServiceCatalogControllerManager
VERSION:  operator.openshift.io/v1

DESCRIPTION:
     <empty>

The explain of "servicecatalogcontrollermanagers" worked but the description is "empty", 
verify this bug and open a new one to track the empty "description" problem. https://bugzilla.redhat.com/show_bug.cgi?id=1770108

Comment 4 errata-xmlrpc 2020-01-23 11:11:03 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-2020:0062