Bug 2104337 - Remove `yq` curls from CI steps
Summary: Remove `yq` curls from CI steps
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.10
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ---
: 4.12.0
Assignee: OCP Installer
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks: 2118514
TreeView+ depends on / blocked
 
Reported: 2022-07-06 02:18 UTC by Johnny Liu
Modified: 2023-01-17 19:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2118514 (view as bug list)
Environment:
Last Closed: 2023-01-17 19:51:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 6008 0 None open Download `yq` in upi installer containers 2022-07-06 02:19:33 UTC
Red Hat Product Errata RHSA-2022:7399 0 None None None 2023-01-17 19:51:44 UTC

Description Johnny Liu 2022-07-06 02:18:59 UTC
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.

Comment 1 Johnny Liu 2022-08-16 02:37:17 UTC
The PR get merged, and test jobs get passed.

Comment 4 errata-xmlrpc 2023-01-17 19:51:26 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.12.0 bug fix and 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:7399


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