[release-4.19] OCPBUGS-80500: Bump google.golang.org/grpc to v1.79.3 by ocp-sustaining-admins · Pull Request #307 · openshift/prometheus

ocp-sustaining-admins · 2026-05-01T15:45:49Z

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: ., documentation/examples/remote_storage, web/ui/mantine-ui/src/promql/tools

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

Note: This package bump updated the go directive in go.mod. This may cause CI check failures if the repository's CI configuration does not yet support the updated Go version.

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

openshift-ci-robot · 2026-05-01T15:45:56Z

@ocp-sustaining-admins: This pull request references Jira Issue OCPBUGS-80500, 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-80500 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: ., documentation/examples/remote_storage, web/ui/mantine-ui/src/promql/tools

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
Note: This package bump updated the go directive in go.mod. This may cause CI check failures if the repository's CI configuration does not yet support the updated Go version.

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 · 2026-05-01T15:45:57Z

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: 75b9179d-cca5-470b-8383-5ec421977562

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 · 2026-05-01T15:46:02Z

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.

shannon · 2026-05-01T17:00:38Z

/ok-to-test

simonpasquier · 2026-05-12T13:38:42Z

/test e2e-aws-ovn-upgrade

simonpasquier · 2026-05-12T13:38:53Z

/label backport-risk-assessed

simonpasquier · 2026-05-19T09:02:00Z

/jira refresh

openshift-ci-robot · 2026-05-19T09:02:08Z

@simonpasquier: This pull request references Jira Issue OCPBUGS-80500, 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-80500 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.

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.

simonpasquier · 2026-05-19T09:23:27Z

/jira refresh

openshift-ci-robot · 2026-05-19T09:23:32Z

@simonpasquier: This pull request references Jira Issue OCPBUGS-80500, which is invalid:

expected dependent Jira Issue OCPBUGS-80678 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED 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.

simonpasquier · 2026-05-19T09:24:26Z

/approve

rhdmalone · 2026-05-29T16:37:11Z

/test common-test

simonpasquier · 2026-06-01T07:54:33Z

/override ci/prow/common-test

The unit tests are failing because of the otel library bump. Since otel configuration isn't exposed in OCP, there's no impact.

openshift-ci · 2026-06-01T07:55:10Z

@simonpasquier: Overrode contexts on behalf of simonpasquier: ci/prow/common-test

Details

In response to this:

/override ci/prow/common-test

The unit tests are failing because of the otel library bump. Since otel configuration isn't exposed in OCP, there's no impact.

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.

rhdmalone · 2026-06-02T09:33:14Z

/verified by CI

openshift-ci-robot · 2026-06-02T09:33:18Z

@rhdmalone: Jira verification commands are restricted to collaborators for this repo.

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.

Bump semconv import from v1.26.0 to v1.34.0 to match the version used internally by the OTel SDK v1.37.0 built-in resource detectors (WithProcessRuntimeDescription, WithTelemetrySDK). The mismatch caused all tracing tests to fail with: error detecting resource: conflicting Schema URL: https://opentelemetry.io/schemas/1.26.0 and https://opentelemetry.io/schemas/1.34.0 Related: OCPBUGS-80500

simonpasquier

/lgtm

Fix OTel semconv schema URL conflict (tracing/tracing.go)

rhdmalone · 2026-06-02T16:22:13Z

hi @simonpasquier
I made one further modification to the PR:
tracing/tracing.go
semconv "go.opentelemetry.io/otel/semconv/v1.34.0"
as the OTEL SDK was updated to v1.37.0
So the PR needs LGTM and verified labels
Thanks very much

rhdmalone · 2026-06-03T09:08:22Z

/test e2e-agnostic-cmo

simonpasquier · 2026-06-03T09:09:33Z

/jira refresh

openshift-ci-robot · 2026-06-03T09:09:40Z

@simonpasquier: This pull request references Jira Issue OCPBUGS-80500, which is valid.

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 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-80678 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-80678 targets the "4.20.z" version, which is one of the valid target versions: 4.20.0, 4.20.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

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.

simonpasquier · 2026-06-03T09:10:04Z

/lgtm
/verified by @simonpasquier

openshift-ci-robot · 2026-06-03T09:10:09Z

@simonpasquier: This PR has been marked as verified by @simonpasquier.

Details

In response to this:

/lgtm
/verified by @simonpasquier

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 · 2026-06-03T09:10:29Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ocp-sustaining-admins, simonpasquier

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~~ [simonpasquier]

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

openshift-ci · 2026-06-03T12:45:47Z

@ocp-sustaining-admins: 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.

openshift-ci-robot · 2026-06-03T12:50:17Z

@ocp-sustaining-admins: Jira Issue Verification Checks: Jira Issue OCPBUGS-80500
✔️ 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-80500 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:

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: ., documentation/examples/remote_storage, web/ui/mantine-ui/src/promql/tools

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
Note: This package bump updated the go directive in go.mod. This may cause CI check failures if the repository's CI configuration does not yet support the updated Go version.

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.

rhdmalone · 2026-06-03T15:50:15Z

/jira refresh

openshift-ci-robot · 2026-06-03T15:50:18Z

@rhdmalone: No Jira issue with key OCPBUGS-80500 exists in the tracker at https://redhat.atlassian.net.
Once a valid jira issue is referenced in the title of this pull request, request a refresh with /jira refresh.

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-merge-robot · 2026-06-04T05:35:54Z

Fix included in release 4.19.0-0.nightly-2026-06-03-215409

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

f78ec63

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 Bot requested review from machine424 and rexagod May 1, 2026 15:46

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 Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label May 12, 2026

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 19, 2026

rhdmalone mentioned this pull request Jun 2, 2026

Fix OTel semconv schema URL conflict (tracing/tracing.go) openshift-sustaining/openshift--prometheus#1

Merged

simonpasquier reviewed Jun 2, 2026

View reviewed changes

openshift-ci Bot assigned simonpasquier Jun 2, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 2, 2026

Merge pull request #1 from rhdmalone/release-4.19_CVE-2026-33186

264e8dc

Fix OTel semconv schema URL conflict (tracing/tracing.go)

openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Jun 2, 2026

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 Jun 3, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Jun 3, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 3, 2026

openshift-merge-bot Bot merged commit ff416b8 into openshift:release-4.19 Jun 3, 2026
10 checks passed

Conversation

ocp-sustaining-admins commented May 1, 2026

Uh oh!

openshift-ci-robot commented May 1, 2026

Uh oh!

coderabbitai Bot commented May 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

openshift-ci Bot commented May 1, 2026

Uh oh!

shannon commented May 1, 2026

Uh oh!

simonpasquier commented May 12, 2026

Uh oh!

simonpasquier commented May 12, 2026

Uh oh!

simonpasquier commented May 19, 2026

Uh oh!

openshift-ci-robot commented May 19, 2026

Uh oh!

simonpasquier commented May 19, 2026

Uh oh!

openshift-ci-robot commented May 19, 2026

Uh oh!

simonpasquier commented May 19, 2026

Uh oh!

rhdmalone commented May 29, 2026

Uh oh!

simonpasquier commented Jun 1, 2026

Uh oh!

openshift-ci Bot commented Jun 1, 2026

Uh oh!

rhdmalone commented Jun 2, 2026

Uh oh!

openshift-ci-robot commented Jun 2, 2026

Uh oh!

simonpasquier left a comment

Choose a reason for hiding this comment

Uh oh!

rhdmalone commented Jun 2, 2026

Uh oh!

rhdmalone commented Jun 3, 2026

Uh oh!

simonpasquier commented Jun 3, 2026

Uh oh!

openshift-ci-robot commented Jun 3, 2026

Uh oh!

simonpasquier commented Jun 3, 2026

Uh oh!

openshift-ci-robot commented Jun 3, 2026

Uh oh!

openshift-ci Bot commented Jun 3, 2026

Uh oh!

openshift-ci Bot commented Jun 3, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Jun 3, 2026

Uh oh!

rhdmalone commented Jun 3, 2026

Uh oh!

openshift-ci-robot commented Jun 3, 2026

Uh oh!

openshift-merge-robot commented Jun 4, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

coderabbitai Bot commented May 1, 2026 •

edited

Loading