OCPBUGS-80595: Bump google.golang.org/grpc to v1.79.3

[ocp-sustaining-admins]

This PR is part of an automated process.

The commands used to generate this PR were:

go get google.golang.org/grpc@v1.79.3 toolchain@none
go mod tidy
go mod vendor

A member of the Red Hat Openshift Sustaining Team will review the PR and take appropriate action.

[openshift-ci-robot]

@ocp-sustaining-admins: This pull request references Jira Issue OCPBUGS-80595, 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-80595 to depend on a bug targeting a version in 4.21.0, 4.21.z 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:

This PR is part of an automated process.

The commands used to generate this PR were:

go get google.golang.org/grpc@v1.79.3 toolchain@none
go mod tidy
go mod vendor

A member of the Red Hat Openshift Sustaining Team will review the PR and take appropriate action.

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-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ocp-sustaining-admins
Once this PR has been reviewed and has the lgtm label, please assign yanirq for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci]

Hi @ocp-sustaining-admins. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)

• do-not-merge/work-in-progress

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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5c919142-0ec2-4dc0-8e8a-13c2784040c8

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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 and usage tips.}

[jmencak]

/ok-to-test

[openshift-ci]

@ocp-sustaining-admins: 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/verify-deps	75470f9	link	true	/test verify-deps
ci/prow/e2e-hypershift	75470f9	link	true	/test e2e-hypershift
ci/prow/images	75470f9	link	true	/test images
ci/prow/lint	75470f9	link	true	/test lint
ci/prow/e2e-aws-operator	75470f9	link	true	/test e2e-aws-operator
ci/prow/vet	75470f9	link	true	/test vet
ci/prow/e2e-hypershift-pao	75470f9	link	true	/test e2e-hypershift-pao
ci/prow/e2e-upgrade	75470f9	link	true	/test e2e-upgrade
ci/prow/e2e-no-cluster	75470f9	link	true	/test e2e-no-cluster
ci/prow/e2e-gcp-pao	75470f9	link	true	/test e2e-gcp-pao
ci/prow/e2e-gcp-pao-workloadhints	75470f9	link	true	/test e2e-gcp-pao-workloadhints
ci/prow/e2e-aws-ovn	75470f9	link	true	/test e2e-aws-ovn
ci/prow/e2e-aws-ovn-techpreview	75470f9	link	true	/test e2e-aws-ovn-techpreview
ci/prow/e2e-gcp-pao-updating-profile	75470f9	link	true	/test e2e-gcp-pao-updating-profile
ci/prow/unit	75470f9	link	true	/test unit

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.

[jmencak]

Hmm, this doesn't look ready. We need the same fix in the main branch and 4.21 too first.