Skip to content

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

Open
pmtk wants to merge 3 commits intoopenshift:release-4.17from
pmtk:grpc-cve-4.17
Open

[release-4.17] OCPBUGS-80182: Replace google.golang.org/grpc with openshift-sustaining fork#6528
pmtk wants to merge 3 commits intoopenshift:release-4.17from
pmtk:grpc-cve-4.17

Conversation

@pmtk
Copy link
Copy Markdown
Member

@pmtk pmtk commented Apr 17, 2026

No description provided.

@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 Apr 17, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@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
Copy link
Copy Markdown

coderabbitai bot commented Apr 17, 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: Pro Plus

Run ID: dc4aec09-2733-4e1f-8614-926d31d55bea

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.

@openshift-ci openshift-ci bot requested review from copejon and jogeo April 17, 2026 12:53
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 17, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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:

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 Apr 17, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci bot commented Apr 17, 2026

@pmtk: 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/footprint-and-performance 9c3fbc0 link true /test footprint-and-performance
ci/prow/ocp-conformance-with-optional-rpms-rhel-eus-nightly-arm 9c3fbc0 link true /test ocp-conformance-with-optional-rpms-rhel-eus-nightly-arm
ci/prow/verify 9c3fbc0 link true /test verify
ci/prow/metal-periodic-test 9c3fbc0 link true /test metal-periodic-test
ci/prow/microshift-metal-tests 9c3fbc0 link true /test microshift-metal-tests
ci/prow/metal-bootc-test 9c3fbc0 link true /test metal-bootc-test
ci/prow/microshift-metal-cache-arm 9c3fbc0 link true /test microshift-metal-cache-arm
ci/prow/microshift-metal-tests-arm 9c3fbc0 link true /test microshift-metal-tests-arm
ci/prow/e2e-aws-nvidia-device-plugin 9c3fbc0 link true /test e2e-aws-nvidia-device-plugin
ci/prow/metal-bootc-periodic-test 9c3fbc0 link true /test metal-bootc-periodic-test
ci/prow/microshift-metal-cache 9c3fbc0 link true /test microshift-metal-cache
ci/prow/metal-bootc-test-arm 9c3fbc0 link true /test metal-bootc-test-arm
ci/prow/metal-periodic-test-arm 9c3fbc0 link true /test metal-periodic-test-arm
ci/prow/ocp-full-conformance-rhel-eus 9c3fbc0 link true /test ocp-full-conformance-rhel-eus
ci/prow/test-unit 9c3fbc0 link true /test test-unit
ci/prow/metal-bootc-periodic-test-arm 9c3fbc0 link true /test metal-bootc-periodic-test-arm
ci/prow/ocp-conformance-with-optional-rpms-rhel-eus-nightly 9c3fbc0 link true /test ocp-conformance-with-optional-rpms-rhel-eus-nightly

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. 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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants