Bug 1926588 - The tarball of operator-sdk is not ready for ocp4.7
Summary: The tarball of operator-sdk is not ready for ocp4.7
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Release
Version: 4.7
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 4.7.0
Assignee: Luke Meyer
QA Contact: Fan Jia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-02-09 06:39 UTC by Fan Jia
Modified: 2021-02-24 15:58 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 15:58:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift aos-cd-jobs pull 2524 0 None closed [ART-2459] Update operator-sdk_sync job 2021-02-18 03:03:09 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:58:38 UTC

Description Fan Jia 2021-02-09 06:39:14 UTC 
Description of problem:
The tarball of operator-sdk is not ready for ocp4.7
https://mirror.openshift.com/pub/openshift-v4/clients/

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Jesus M. Rodriguez 2021-02-09 18:37:56 UTC 
This is required for the downstream supported version of operator-sdk to be available for 4.7 release.
Comment 5 Fan Jia 2021-02-10 00:44:24 UTC 
Verified this bug
Comment 8 errata-xmlrpc 2021-02-24 15:58:19 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.7.0 security, bug fix, and enhancement 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-2020:5633
Note You need to log in before you can comment on or make changes to this bug.