OCPBUGS-112029: Bump google-cloud-cli to 563.0.0-1

[redhat-chai-bot]

Backport of #10460 to release-4.21.

The pinned google-cloud-cli-447.0.0-1 version is no longer available in the Google Cloud SDK yum repo, causing 100% x86_64 build failures for OKD okd-only-upi-installer since early August.

This bumps the pin to 563.0.0-1 (matching the fix already landed on the main branch via #10460).

---

AI-generated. Review for accuracy.

@locriandev requested in Slack thread

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 03ea0433-eae0-4e9a-b50e-2a576cd9f904

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[locriandev]

/retitle "ART-22774: Bump google-cloud-cli to 563.0.0-1"

[openshift-ci-robot]

@redhat-chai-bot: This pull request references ART-22774 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the ticket to target the "4.21.z" version, but no target version was set.

Details

In response to this:

Backport of #10460 to release-4.21.

The pinned google-cloud-cli-447.0.0-1 version is no longer available in the Google Cloud SDK yum repo, causing 100% x86_64 build failures for OKD okd-only-upi-installer since early August.

This bumps the pin to 563.0.0-1 (matching the fix already landed on the main branch via #10460).

---

AI-generated. Review for accuracy.

@locriandev requested in Slack thread

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 openshift-eng/jira-lifecycle-plugin repository.

[locriandev]

/retitle ART-22774: Bump google-cloud-cli to 563.0.0-1

[tthvo]

/lgtm
/approve

As Patrick said, you need an OCPBUGS chain to merge backports 😁

[openshift-merge-bot]

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-aws-ovn-upi
/test e2e-azure-ovn-upi
/test e2e-gcp-ovn-upi
/test e2e-vsphere-ovn-upi
/test e2e-vsphere-ovn-upi-zones
/test e2e-aws-ovn

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tthvo

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 [tthvo]

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

[redhat-chai-bot]

/retest-required

e2e-gcp-ovn-upi failed due to GCP zone capacity exhaustion (ZONE_RESOURCE_POOL_EXHAUSTED in us-central1-c), not related to this change.

---

AI-generated. Review for accuracy.

[redhat-chai-bot]

/retest-required

e2e-gcp-ovn-upi failed again after a full 9h run — likely a flaky e2e test, unrelated to this one-line google-cloud-cli version bump.

---

AI-generated. Review for accuracy.

[locriandev]

/retest-required

[locriandev]

/retitle OCPBUGS-112029: Bump google-cloud-cli to 563.0.0-1

[openshift-ci-robot]

@redhat-chai-bot: This pull request references Jira Issue OCPBUGS-112029, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-112029 to depend on a bug targeting a version in 4.22.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Backport of #10460 to release-4.21.

The pinned google-cloud-cli-447.0.0-1 version is no longer available in the Google Cloud SDK yum repo, causing 100% x86_64 build failures for OKD okd-only-upi-installer since early August.

This bumps the pin to 563.0.0-1 (matching the fix already landed on the main branch via #10460).

---

AI-generated. Review for accuracy.

@locriandev requested in Slack thread

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 openshift-eng/jira-lifecycle-plugin repository.

[locriandev]

/jira refresh

[openshift-ci-robot]

@locriandev: This pull request references Jira Issue OCPBUGS-112029, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead
• expected Jira Issue OCPBUGS-112029 to depend on a bug targeting a version in 4.22.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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

Details

In response to this:

/jira 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 openshift-eng/jira-lifecycle-plugin repository.

[locriandev]

/jira refresh

[openshift-ci-robot]

@locriandev: This pull request references Jira Issue OCPBUGS-112029, which is invalid:

• expected Jira Issue OCPBUGS-112029 to depend on a bug targeting a version in 4.22.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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

Details

In response to this:

/jira 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 openshift-eng/jira-lifecycle-plugin repository.

[locriandev]

/jira refresh

[openshift-ci-robot]

@locriandev: This pull request references Jira Issue OCPBUGS-112029, which is invalid:

• expected dependent Jira Issue OCPBUGS-112028 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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

Details

In response to this:

/jira 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 openshift-eng/jira-lifecycle-plugin repository.

[sadasu]

/label backport-risk-assessed

[sadasu]

/verified by CI

[openshift-ci-robot]

@sadasu: This PR has been marked as verified by CI.

Details

In response to this:

/verified by 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 openshift-eng/jira-lifecycle-plugin repository.

[locriandev]

/jira refresh

[openshift-ci-robot]

@locriandev: This pull request references Jira Issue OCPBUGS-112029, which is invalid:

• expected dependent Jira Issue OCPBUGS-112028 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

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

Details

In response to this:

/jira 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 openshift-eng/jira-lifecycle-plugin repository.

[locriandev]

/jira refresh

[openshift-ci-robot]

@locriandev: This pull request references Jira Issue OCPBUGS-112029, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.21.z) matches configured target version for branch (4.21.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-112028 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-112028 targets the "4.22.z" version, which is one of the valid target versions: 4.22.0
• bug has dependents

Details

In response to this:

/jira 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 openshift-eng/jira-lifecycle-plugin repository.

[locriandev]

/retest-required

[openshift-merge-bot]

/retest-required

Remaining retests: 0 against base HEAD 129c91f and 2 for PR HEAD 4c86ea0 in total

[tthvo]

/override-sticky ci/prow/e2e-gcp-ovn-upi

The pre-install set-up and install completed successfully. Other e2e failures are unrelated.

[openshift-ci]

@tthvo: Overrode contexts on behalf of tthvo: ci/prow/e2e-gcp-ovn-upi

These overrides will persist across retests on the current HEAD SHA. Pushing a new commit will clear them. Use /override-cancel to remove them.

Details

In response to this:

/override-sticky ci/prow/e2e-gcp-ovn-upi

The pre-install set-up and install completed successfully. Other e2e failures are unrelated.

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-sigs/prow repository.

[tthvo]

/tide refresh

[openshift-ci]

@redhat-chai-bot: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-azure-ovn-upi	4c86ea0	link	false	/test e2e-azure-ovn-upi
ci/prow/e2e-vsphere-ovn-upi-zones	4c86ea0	link	false	/test e2e-vsphere-ovn-upi-zones
ci/prow/e2e-gcp-ovn-upi	4c86ea0	link	true	/test e2e-gcp-ovn-upi

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-sigs/prow repository. I understand the commands that are listed here.

[openshift-ci-robot]

@redhat-chai-bot: Jira Issue Verification Checks: Jira Issue OCPBUGS-112029
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-112029 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Backport of #10460 to release-4.21.

The pinned google-cloud-cli-447.0.0-1 version is no longer available in the Google Cloud SDK yum repo, causing 100% x86_64 build failures for OKD okd-only-upi-installer since early August.

This bumps the pin to 563.0.0-1 (matching the fix already landed on the main branch via #10460).

---

AI-generated. Review for accuracy.

@locriandev requested in Slack thread

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-merge-robot]

Fix included in release 4.21.0-0.nightly-2026-08-22-094635