[release-4.17] OCPBUGS-80007: Replace google.golang.org/grpc with openshift-sustaining fork by pmtk · Pull Request #6528 · openshift/microshift

pmtk · 2026-04-17T12:52:55Z

No description provided.

openshift-ci-robot · 2026-04-17T12:53:02Z

@pmtk: This pull request references Jira Issue OCPBUGS-80182, which is invalid:

expected the vulnerability to target either version "4.17." or "openshift-4.17.", but it targets "4.18.z" 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 dependent Jira Issue OCPBUGS-80315 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New 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.

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

Details

In response to this:

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-04-17T12:53:02Z

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: 2cbb206a-516a-42f1-8bf7-33300a7ccd39

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

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

pacevedom · 2026-04-22T13:45:00Z

/retest
/jira refresh

openshift-ci-robot · 2026-04-22T13:45:06Z

@pacevedom: This pull request references Jira Issue OCPBUGS-80182, which is invalid:

expected the vulnerability to target either version "4.17." or "openshift-4.17.", but it targets "4.18.z" 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.

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:

/retest
/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 · 2026-04-22T17:18:08Z

@pmtk: 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.

pacevedom

/lgtm

pacevedom · 2026-04-22T20:59:36Z

/label backport-risk-assessed
/verified by CI
/jira refresh

openshift-ci · 2026-04-22T20:59:43Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pacevedom, pmtk

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~~ [pacevedom,pmtk]

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

openshift-ci-robot · 2026-04-22T20:59:48Z

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

Details

In response to this:

/label backport-risk-assessed
/verified by CI
/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-robot · 2026-04-22T20:59:50Z

@pacevedom: This pull request references Jira Issue OCPBUGS-80182, which is invalid:

expected the vulnerability to target either version "4.17." or "openshift-4.17.", but it targets "4.18.z" 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.

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:

/label backport-risk-assessed
/verified by CI
/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.

pacevedom · 2026-04-23T07:35:09Z

/retitle [release-4.17] OCPBUGS-80007: Replace google.golang.org/grpc with openshift-sustaining fork

openshift-ci-robot · 2026-04-23T07:35:17Z

@pmtk: This pull request references Jira Issue OCPBUGS-80007, 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 dependent Jira Issue OCPBUGS-80182 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.

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

Details

In response to this:

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.

pacevedom · 2026-04-23T07:40:03Z

/jira refresh

openshift-ci-robot · 2026-04-23T07:40:09Z

@pacevedom: This pull request references Jira Issue OCPBUGS-80007, 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 dependent Jira Issue OCPBUGS-80182 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.

pacevedom · 2026-04-23T07:44:41Z

/jira refresh

openshift-ci-robot · 2026-04-23T07:44:47Z

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

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.

pacevedom · 2026-04-23T07:45:28Z

/jira refresh

openshift-ci-robot · 2026-04-23T07:45:34Z

@pacevedom: This pull request references Jira Issue OCPBUGS-80007, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.17.z) matches configured target version for branch (4.17.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-80182 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-80182 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
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.

openshift-ci-robot · 2026-04-23T07:50:03Z

@pmtk: Jira Issue OCPBUGS-80007: All pull requests linked via external trackers have merged:

openshift/microshift#6528

All linked pull requests have the verified tag. Jira Issue OCPBUGS-80007 has been moved to the VERIFIED state.

Details

In response to this:

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.

pmtk added 2 commits April 17, 2026 14:07

Replace google.golang.org/grpc with openshift-sustaining

cce003a

etcd: tidy & vendor

eaffed5

openshift-ci Bot requested review from copejon and jogeo April 17, 2026 12:53

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

microshift: tidy & vendor

84be1b1

pmtk force-pushed the grpc-cve-4.17 branch from 9c3fbc0 to 84be1b1 Compare April 22, 2026 14:58

pacevedom approved these changes Apr 22, 2026

View reviewed changes

openshift-ci Bot assigned pacevedom Apr 22, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Apr 22, 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 Apr 22, 2026

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

openshift-ci Bot changed the title ~~[release-4.17] OCPBUGS-80182: Replace google.golang.org/grpc with openshift-sustaining fork~~ [release-4.17] OCPBUGS-80007: Replace google.golang.org/grpc with openshift-sustaining fork Apr 23, 2026

openshift-ci-robot mentioned this pull request Apr 23, 2026

[release-4.18] OCPBUGS-80182: Replace google.golang.org/grpc with openshift-sustaining fork #6527

Merged

openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Apr 23, 2026

openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Apr 23, 2026

openshift-merge-bot Bot merged commit 3f6b843 into openshift:release-4.17 Apr 23, 2026
21 checks passed

Conversation

pmtk commented Apr 17, 2026

Uh oh!

openshift-ci-robot commented Apr 17, 2026

Uh oh!

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

Uh oh!

Review skipped

Uh oh!

pacevedom commented Apr 22, 2026

Uh oh!

openshift-ci-robot commented Apr 22, 2026

Uh oh!

openshift-ci Bot commented Apr 22, 2026

Uh oh!

pacevedom left a comment

Choose a reason for hiding this comment

Uh oh!

pacevedom commented Apr 22, 2026

Uh oh!

openshift-ci Bot commented Apr 22, 2026

Uh oh!

openshift-ci-robot commented Apr 22, 2026

Uh oh!

openshift-ci-robot commented Apr 22, 2026

Uh oh!

pacevedom commented Apr 23, 2026

Uh oh!

openshift-ci-robot commented Apr 23, 2026

Uh oh!

pacevedom commented Apr 23, 2026

Uh oh!

openshift-ci-robot commented Apr 23, 2026

Uh oh!

pacevedom commented Apr 23, 2026

Uh oh!

openshift-ci-robot commented Apr 23, 2026

Uh oh!

pacevedom commented Apr 23, 2026

Uh oh!

openshift-ci-robot commented Apr 23, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Apr 23, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

coderabbitai Bot commented Apr 17, 2026 •

edited

Loading