Hide Forgot
Description of problem: Copied from bug 1705746, should add the description info for these CRDs so that `oc explain` can work. mac:beta5 jianzhang$ oc explain operatorsource|grep -i description -A 3 DESCRIPTION: <empty> mac:beta5 jianzhang$ oc explain csc|grep -i description -A 3 DESCRIPTION: <empty> Version-Release number of selected component (if applicable): Cluster version is 4.1.0-rc.2 How reproducible: always Steps to Reproduce: 1. Install the OCP 4.1. 2. Login this cluster as a cluster-admin. 3. Check the two CRDs and run the commands below in the backend. $ oc explain operatorsource|grep -i description -A 3 $ oc explain csc|grep -i description -A 3 Actual results: Get nothing about the descrioption. mac:beta5 jianzhang$ oc explain operatorsource|grep -i description -A 3 DESCRIPTION: <empty> mac:beta5 jianzhang$ oc explain csc|grep -i description -A 3 DESCRIPTION: <empty> Expected results: Should get the appropriate description for those two CRDs. Additional info:
The following PR has been opened to address this bug: https://github.com/operator-framework/operator-marketplace/pull/185 Problem: The CatalogSourceConfig and OperatorSource Custom Resource Definitions (CRD) are missing the openapi definition fields. Solution: Update the CRDs with the `spec.validation.openAPIV3Schema.description` field.
The PR above has been merged.
The latest nightly build (4.1.0-0.nightly-2019-05-16-223922) doesn't include the pr , will test until it includes it.
The latest nightly build (4.1.0-0.nightly-2019-05-17-041605) doesn't include the pr , will test until it includes it.
The branch release-4.1 doesn't include this pr, will be tested in 4.1.z.
A new PR was created to add this to the 4.1 branch: https://github.com/operator-framework/operator-marketplace/pull/218
That PR was closed, and resurrected as an automated cherry-pick https://github.com/operator-framework/operator-marketplace/pull/219 which merged and was built, but nothing updated this bug.
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-2019:1809