Bug 1946307 - [CI] [UPI] use a standardized and reliable way to install google cloud SDK in UPI image
Summary: [CI] [UPI] use a standardized and reliable way to install google cloud SDK in...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.8
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.8.0
Assignee: Etienne Simard
QA Contact: Gaoyun Pei
Depends On:
Blocks: 1947122
TreeView+ depends on / blocked
Reported: 2021-04-05 18:41 UTC by Etienne Simard
Modified: 2021-07-27 22:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
This is a CI-only fix.
Clone Of:
Last Closed: 2021-07-27 22:57:19 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift installer pull 4819 0 None open Bug 1946307: gcp: install google cloud sdk with yum the recommended way 2021-04-05 18:56:33 UTC
Red Hat Product Errata RHSA-2021:2438 0 None None None 2021-07-27 22:57:46 UTC

Description Etienne Simard 2021-04-05 18:41:39 UTC



GCP, but the failure affects CI from other other platforms because the failure affects all tests using the UPI image.

Please specify:


What happened?

repomd.xml signature could not be verified when trying to install google cloud sdk with yum with repo_gpgcheck=1 enabled

This is a known Google Cloud issue:



To fix this, disable repository GPG key checking in the yum repo configuration by setting repo_gpgcheck=0. In supported Compute Engine base images this setting might be found in /etc/yum.repos.d/google-cloud.repo file. However, your VM can have this set in different repository configuration files or automation tools.

Yum repositories do not usually use GPG keys for repository validation. Instead, the https endpoint is trusted."

Additional info: 


Comment 1 Matthew Staebler 2021-04-05 20:30:13 UTC
I upped the severity and priority to urgent since this is blocking ALL installer PRs from merging.

Comment 6 errata-xmlrpc 2021-07-27 22:57: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.8.2 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.


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