Description of problem: Should add the description info for CRD servicecatalogcontrollermanagers. #oc explain servicecatalogcontrollermanagers|grep -i description -A 3 DESCRIPTION: <empty> Version-Release number of selected component (if applicable): 4.3.0-0.nightly-2019-11-07-172437 How reproducible: always Steps to Reproduce: 1. Install the OCP 4.3. 2. Login this cluster as a cluster-admin. 3. Check the CRD servicecatalogcontrollermanagers $ oc explain servicecatalogcontrollermanagers|grep -i description -A 3 Actual results: Get nothing about the descrioption. #oc explain servicecatalogcontrollermanagers|grep -i description -A 3 DESCRIPTION: <empty> Expected results: Should get the appropriate description for CRD servicecatalogcontrollermanagers Additional info:
test env: cv:4.3.0-0.nightly-2019-11-19-053808 test result: $ oc explain servicecatalogcontrollermanagers KIND: ServiceCatalogControllerManager VERSION: operator.openshift.io/v1 DESCRIPTION: ServiceCatalogControllerManager provides information to configure an operator to manage Service Catalog Controller Manager FIELDS: apiVersion <string> APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources kind <string> Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds metadata <Object> Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata spec <Object> -required- status <Object>
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