Skip to content

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

Open
ocp-sustaining-admins wants to merge 1 commit intoopenshift:release-4.19from
openshift-sustaining:release-4.19_CVE-2026-33186
Open

[release-4.19] OCPBUGS-80419: Bump google.golang.org/grpc to v1.79.3#1501
ocp-sustaining-admins wants to merge 1 commit intoopenshift:release-4.19from
openshift-sustaining:release-4.19_CVE-2026-33186

Conversation

@ocp-sustaining-admins
Copy link
Copy Markdown

This is an automated PR from the ARC system.

Go version used: go1.23.12

Patch applied: github.com/openshift-sustaining/grpc-go@v1.75.1-sec.1

Modules affected: .

The commands used to generate this PR were:

go mod edit -replace google.golang.org/grpc=github.com/openshift-sustaining/grpc-go@v1.75.1-sec.1
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 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. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 1, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@ocp-sustaining-admins: This pull request references Jira Issue OCPBUGS-80419, which is invalid:

  • expected the bug to be open, but it isn't
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Not a Bug) instead
  • 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-80419 to depend on a bug targeting a version in 4.20.0, 4.20.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 is an automated PR from the ARC system.

Go version used: go1.23.12

Patch applied: github.com/openshift-sustaining/grpc-go@v1.75.1-sec.1

Modules affected: .

The commands used to generate this PR were:

go mod edit -replace google.golang.org/grpc=github.com/openshift-sustaining/grpc-go@v1.75.1-sec.1
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.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 1, 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: 85a7a2eb-8ff2-4ee1-aae5-614235688080

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.

@qodo-code-review
Copy link
Copy Markdown

Review Summary by Qodo

Bump google.golang.org/grpc and update dependencies

✨ Enhancement

Grey Divider

Walkthroughs

Description
• Bump google.golang.org/grpc to v1.75.1-sec.1 via replace directive
• Update OpenTelemetry dependencies to v1.37.0
• Update golang.org/x dependencies to latest versions
• Update cel.dev/expr and go-logr/logr to newer versions
Diagram
flowchart LR
  A["go.mod dependencies"] -- "Update indirect deps" --> B["OpenTelemetry v1.37.0"]
  A -- "Update indirect deps" --> C["golang.org/x packages"]
  A -- "Add replace directive" --> D["grpc-go v1.75.1-sec.1"]
  A -- "Update indirect deps" --> E["Other packages"]
Loading

Grey Divider

File Changes

1. go.mod Dependencies +22/-20

Update dependencies and add grpc replace directive

• Added replace directive for google.golang.org/grpc pointing to
 github.com/openshift-sustaining/grpc-go v1.75.1-sec.1
• Updated go.opentelemetry.io/otel and related packages from v1.34.0 to v1.37.0
• Updated golang.org/x/* packages to latest versions (crypto v0.39.0, net v0.41.0, sys v0.33.0,
 tools v0.33.0, etc.)
• Updated cel.dev/expr from v0.19.0 to v0.24.0 and github.com/go-logr/logr from v1.4.2 to v1.4.3
• Updated google.golang.org/protobuf from v1.36.5 to v1.36.6 and google.golang.org/grpc from
 v1.70.0 to v1.71.0

go.mod


2. go.sum Dependencies +1802/-50

Update dependency checksums

• Updated checksums for all modified dependencies in go.mod
• Added checksums for new dependency versions

go.sum


Grey Divider

Qodo Logo

@qodo-code-review
Copy link
Copy Markdown

qodo-code-review Bot commented May 1, 2026

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0)

Grey Divider


Action required

1. grpc version ambiguous 🐞 Bug ⚙ Maintainability
Description
go.mod now declares google.golang.org/grpc v1.71.0 but replaces it with
github.com/openshift-sustaining/grpc-go v1.75.1-sec.1, so the effective grpc code differs from the
declared grpc version in the module graph. This makes dependency tracking and future go mod
tidy/vendor regeneration error-prone because removing/altering the replace will silently drop back
to v1.71.0.
Code

go.mod[244]

+replace google.golang.org/grpc => github.com/openshift-sustaining/grpc-go v1.75.1-sec.1
Evidence
The PR adds a replace directive to a forked grpc module/version while leaving the required grpc
version at v1.71.0; vendor metadata records this mismatch explicitly, and go.sum confirms the fork
version being used.

go.mod[156-181]
go.mod[240-244]
vendor/modules.txt[939-951]
go.sum[1528-1532]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`go.mod` declares `google.golang.org/grpc v1.71.0` but also replaces it with `github.com/openshift-sustaining/grpc-go v1.75.1-sec.1`, making the effective grpc code version differ from the declared grpc version.

### Issue Context
This discrepancy is also reflected in `vendor/modules.txt`, which will commonly be used by tooling/SBOM generation and can be silently reverted by future `go mod tidy`/`go mod vendor` changes if the `replace` line is touched.

### Fix Focus Areas
- go.mod[156-181]
- go.mod[240-244]

### What to change
- Update the declared `require google.golang.org/grpc ...` version to match the intended grpc version (and keep it aligned with the fork’s tag/base).
- Keep (or adjust) the `replace google.golang.org/grpc => github.com/openshift-sustaining/grpc-go ...` to the corresponding fork version.
- Re-run `go mod tidy` and `go mod vendor` to ensure `go.sum` and `vendor/modules.txt` are consistent with the final intended version.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

Qodo Logo

@openshift-ci openshift-ci Bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label May 1, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 1, 2026

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.

@openshift-ci openshift-ci Bot requested review from swatisehgal and yanirq May 1, 2026 16:49
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 1, 2026

[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 marsik 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:

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

Comment thread go.mod
// openshift/openshift-kni/debug-tools@v0.2.1 needs pinning of cadvisor; also gather-sysinfo.go needs to be fixed to allow usage of latest debug-tools
replace github.com/google/cadvisor => github.com/google/cadvisor v0.49.1

replace google.golang.org/grpc => github.com/openshift-sustaining/grpc-go v1.75.1-sec.1
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Grpc version ambiguous 🐞 Bug ⚙ Maintainability

go.mod now declares google.golang.org/grpc v1.71.0 but replaces it with
github.com/openshift-sustaining/grpc-go v1.75.1-sec.1, so the effective grpc code differs from the
declared grpc version in the module graph. This makes dependency tracking and future go mod
tidy/vendor regeneration error-prone because removing/altering the replace will silently drop back
to v1.71.0.
Agent Prompt
### Issue description
`go.mod` declares `google.golang.org/grpc v1.71.0` but also replaces it with `github.com/openshift-sustaining/grpc-go v1.75.1-sec.1`, making the effective grpc code version differ from the declared grpc version.

### Issue Context
This discrepancy is also reflected in `vendor/modules.txt`, which will commonly be used by tooling/SBOM generation and can be silently reverted by future `go mod tidy`/`go mod vendor` changes if the `replace` line is touched.

### Fix Focus Areas
- go.mod[156-181]
- go.mod[240-244]

### What to change
- Update the declared `require google.golang.org/grpc ...` version to match the intended grpc version (and keep it aligned with the fork’s tag/base).
- Keep (or adjust) the `replace google.golang.org/grpc => github.com/openshift-sustaining/grpc-go ...` to the corresponding fork version.
- Re-run `go mod tidy` and `go mod vendor` to ensure `go.sum` and `vendor/modules.txt` are consistent with the final intended version.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

@shannon
Copy link
Copy Markdown

shannon commented May 1, 2026

/ok-to-test

@openshift-ci openshift-ci Bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels May 1, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 1, 2026

@ocp-sustaining-admins: The following test 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-hypershift-pao d1f4909 link true /test e2e-hypershift-pao

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.

@yanirq
Copy link
Copy Markdown
Contributor

yanirq commented May 3, 2026

/cc @jmencak

@openshift-ci openshift-ci Bot requested a review from jmencak May 3, 2026 09:37
@jmencak
Copy link
Copy Markdown
Contributor

jmencak commented May 3, 2026

/cc @jmencak

Well, we have no valid JIRA labels and the backporting does not seem to follow the standard backport practice from the fixed branch down to the unfixed branches.

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

Labels

jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. 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. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants