Bug 2041620 - bundle CSV alm-examples does not parse
Summary: bundle CSV alm-examples does not parse
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.10
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.10.0
Assignee: Roman Bednář
QA Contact: Chao Yang
URL:
Whiteboard:
Depends On:
Blocks: 2044778 2044782
TreeView+ depends on / blocked
 
Reported: 2022-01-17 21:54 UTC by Luke Meyer
Modified: 2022-03-10 16:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2044778 2044782 2044783 2044785 (view as bug list)
Environment:
Last Closed: 2022-03-10 16:40:08 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift local-storage-operator pull 314 0 None open Bug 2041620: bundle CSV alm-examples does not parse 2022-01-20 13:42:02 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:40:32 UTC

Comment 2 Jan Safranek 2022-01-18 14:39:44 UTC 
Newer operator-SDK should validate example JSONs using "operator-sdk bundle validate", see https://github.com/operator-framework/operator-sdk/pull/5495,
Comment 3 Jan Safranek 2022-01-18 15:15:50 UTC 
We need to fix it in all supported branches (up to 4.6.z) because a new check for json validity may be introduced in our build pipeline soon.
Comment 7 Chao Yang 2022-01-21 11:17:44 UTC 
Passed with local-storage-operator.4.10.0-202201201615
Comment 11 errata-xmlrpc 2022-03-10 16:40:08 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 (Moderate: OpenShift Container Platform 4.10.3 security update), 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/RHSA-2022:0056
Note You need to log in before you can comment on or make changes to this bug.