Bug 2118514 - [4.11] Remove `yq` curls from CI steps
Summary: [4.11] Remove `yq` curls from CI steps
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.z
Assignee: OCP Installer
QA Contact: Johnny Liu
Depends On: 2104337
TreeView+ depends on / blocked
Reported: 2022-08-16 02:41 UTC by Johnny Liu
Modified: 2022-08-29 06:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2104337
Last Closed: 2022-08-29 06:46:57 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift installer pull 6225 0 None open Bug 2118514: [4.11] Download yq in upi installer containers 2022-08-16 02:42:35 UTC
Red Hat Product Errata RHBA-2022:6143 0 None None None 2022-08-29 06:47:07 UTC

Description Johnny Liu 2022-08-16 02:41:37 UTC
+++ This bug was initially created as a clone of Bug #2104337 +++

Various CI steps use the upi-installer container for it's access to the
aws cli tools among other things. However, most of those steps also
curl yq directly from GitHub. We can save ourselves some headaches
when GitHub is down by just embedding the binary in the image already.

Whenever GitHub has issues or throttles us, YQ hash mismatch error out. The hash mismatch error is because github is probably returning an error page, although our scripts hide it.

--- Additional comment from Johnny Liu on 2022-08-16 02:37:17 UTC ---

The PR get merged, and test jobs get passed.

Comment 1 Johnny Liu 2022-08-17 06:13:04 UTC
The 4.11 PR get merged, and test jobs get passed.

Comment 4 errata-xmlrpc 2022-08-29 06:46:57 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 (OpenShift Container Platform 4.11.2 bug fix 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.


Note You need to log in before you can comment on or make changes to this bug.