Bug 1946624: Disable repo_gpgcheck for Google Cloud SDK repo in CI

[patrickdillon]

The Google Cloud SDK repo is throwing an error:

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

Disable the GPG check per Google's recommendation:
https://cloud.google.com/compute/docs/troubleshooting/known-issues#known_issues_for_linux_vm_instances

As that doc states:

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

[openshift-ci-robot]

@patrickdillon: This pull request references Bugzilla bug 1946624, which is invalid:

• expected the bug to target the "3.11.z" release, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

Bug 1946624: Disable repo_gpgcheck for Google Cloud SDK repo in CI

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: patrickdillon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [patrickdillon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[patrickdillon]

/bugzilla refresh

[openshift-ci-robot]

@patrickdillon: This pull request references Bugzilla bug 1946624, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (3.11.z) matches configured target release for branch (3.11.z)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (gpei@redhat.com), skipping review request.

Details

In response to this:

/bugzilla refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci]

@patrickdillon: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/images	cea24b4	link	/test images
ci/prow/e2e-aws	cea24b4	link	/test e2e-aws

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[patrickdillon]

This resolves google cloud sdk issue:

Installed:
  google-cloud-sdk.x86_64 0:183.0.0-3.el7                                       

Complete!

But now we're hitting:

Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-3E2qt4/zipp/

[mtnbikenc]

pip failure comment here, for reference, #12315 (comment)

[patrickdillon]

/close
replaced by #12322

[openshift-ci-robot]

@patrickdillon: Closed this PR.

Details

In response to this:

/close
replaced by #12322

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-ci-robot]

@patrickdillon: This pull request references Bugzilla bug 1946624. The bug has been updated to no longer refer to the pull request using the external bug tracker.

Details

In response to this:

Bug 1946624: Disable repo_gpgcheck for Google Cloud SDK repo in CI

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.