Skip to content

[release-4.19] OCPBUGS-80401: Bump google.golang.org/grpc to v1.79.3#295

Open
rh-soboh wants to merge 2 commits into
openshift:release-4.19from
rh-soboh:release-4.19_CVE-2026-33186
Open

[release-4.19] OCPBUGS-80401: Bump google.golang.org/grpc to v1.79.3#295
rh-soboh wants to merge 2 commits into
openshift:release-4.19from
rh-soboh:release-4.19_CVE-2026-33186

Conversation

@rh-soboh
Copy link
Copy Markdown

@rh-soboh rh-soboh commented May 14, 2026

Bump google.golang.org/grpc to address CVE-2026-33186.

Details

  • Go version: go1.22
  • Patch applied: github.com/openshift-sustaining/grpc-go@v1.71.3-sec.1
  • Modules affected: ., hack/tools, openshift/tools, test

Commands used

go mod edit -replace google.golang.org/grpc=github.com/openshift-sustaining/grpc-go@v1.71.3-sec.1
go mod tidy
go mod vendor

Notes

hack/tools required dropping the separate google.golang.org/grpc/stats/opentelemetry sub-module require to resolve an ambiguous import conflict with the replaced main grpc module.

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels May 14, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 14, 2026

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: Enterprise

Run ID: a0cb0fd4-07c9-4a5e-be4e-849c5dba5d5b

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label May 14, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@rh-soboh: This pull request references Jira Issue OCPBUGS-80401, 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.

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 is a manual PR to bump google.golang.org/grpc to address CVE-2026-33186.\n\nGo version used: go1.22\n\nPatch applied: github.com/openshift-sustaining/grpc-go@v1.71.3-sec.1\n\nModules affected: ., hack/tools, openshift/tools, test\n\nThe commands used to generate this PR were:\n\n```\ngo mod edit -replace google.golang.org/grpc=github.com/openshift-sustaining/grpc-go@v1.71.3-sec.1\ngo mod tidy\ngo mod vendor\n```\n\nNote: `hack/tools` required dropping the separate `google.golang.org/grpc/stats/opentelemetry` sub-module require to resolve an ambiguous import conflict with the replaced main grpc module.

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 openshift-ci Bot requested review from JoelSpeed and sub-mod May 14, 2026 09:26
@rh-soboh
Copy link
Copy Markdown
Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 14, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@rh-soboh: This pull request references Jira Issue OCPBUGS-80401, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.z) matches configured target version for branch (4.19.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-80577 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-80577 targets the "4.20.z" version, which is one of the valid target versions: 4.20.0, 4.20.z
  • bug has dependents

Requesting review from QA contact:
/cc @rissh

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.

@openshift-ci openshift-ci Bot requested a review from rissh May 14, 2026 09:29
@JoelSpeed
Copy link
Copy Markdown

/lgtm
/approve
/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label May 14, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 14, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 14, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JoelSpeed, rh-soboh

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:

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 14, 2026
@rh-soboh
Copy link
Copy Markdown
Author

/retest

4 similar comments
@rh-soboh
Copy link
Copy Markdown
Author

/retest

@rissh
Copy link
Copy Markdown

rissh commented May 14, 2026

/retest

@rh-soboh
Copy link
Copy Markdown
Author

/retest

@rh-soboh
Copy link
Copy Markdown
Author

/retest

@rh-soboh
Copy link
Copy Markdown
Author

/test e2e-aws-serial-2of2

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 18, 2026

@rh-soboh: all tests passed!

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants