| Summary: | [marketplace] Missing openapi CRD definitions for oc explain to work | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Aravindh Puthiyaparambil <aravindh> |
| Component: | OLM | Assignee: | Alexander Greene <agreene> |
| OLM sub component: | OperatorHub | QA Contact: | Fan Jia <jfan> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | agreene, bandrade, chezhang, chuo, dyan, jfan, jiazha, scolange, sponnaga, vlaad, xtian |
| Version: | 4.1.0 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.2.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: The CatalogSourceConfig(csc) and OperatorSource(opsrc) CRDs owned by marketplace did not include a description.
Consequence: `oc explain csc` and `oc explain opsrc` would return empty descriptions.
Fix: Add a description to the csc and opsrc CRDs.
Result: `oc explain csc` and `oc explain opsrc` now include descriptions.
|
Story Points: | --- |
| Clone Of: | 1708503 | Environment: | |
| Last Closed: | 2019-10-16 06:32:26 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 1708503 | ||
| Bug Blocks: | |||
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:2922 |
test env: cv:4.2.0-0.nightly-2019-06-24-160709 test result: # oc explain csc|grep -i description -A 3 DESCRIPTION: CatalogSourceConfig is used to enable an operator present in the OperatorSource to your cluster. Behind the scenes, it will configure an OLM CatalogSource so that the operator can then be managed by OLM. # oc explain operatorsource|grep -i description -A 3 DESCRIPTION: OperatorSource is used to define the external datastore we are using to store operator bundles.