Skip to content

DFBUGS-6106:[release-4.20] godeps: update grpc-go version - #792

Merged
openshift-merge-bot[bot] merged 2 commits into
red-hat-storage:release-4.20from
iamniting:CVE-2026-33186-4.20
Jul 21, 2026
Merged

DFBUGS-6106:[release-4.20] godeps: update grpc-go version#792
openshift-merge-bot[bot] merged 2 commits into
red-hat-storage:release-4.20from
iamniting:CVE-2026-33186-4.20

Conversation

@iamniting

Copy link
Copy Markdown
Member

Signed-off-by: Nitin Goyal nigoyal@redhat.com

iamniting added 2 commits May 5, 2026 18:43
Signed-off-by: Nitin Goyal <nigoyal@redhat.com>
Signed-off-by: Nitin Goyal <nigoyal@redhat.com>
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 5, 2026
@iamniting iamniting changed the title [release-4.20] godeps: update grpc-go version DFBUGS-6106:[release-4.20] godeps: update grpc-go version May 5, 2026
@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 the referenced jira bug is invalid for the branch this PR is targeting labels May 5, 2026
@openshift-ci-robot

openshift-ci-robot commented May 5, 2026

Copy link
Copy Markdown

@iamniting: This pull request references [Jira Issue DFBUGS-6106](https://redhat.atlassian.net/browse/DFBUGS-6106), which is invalid:

  • expected the vulnerability to target the "odf-4.20.11" version, but no target version was set

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:

Signed-off-by: Nitin Goyal nigoyal@redhat.com

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.

@iamniting

Copy link
Copy Markdown
Member Author

/test odf-operator-e2e-aws

@iamniting

Copy link
Copy Markdown
Member Author

/override ci/prow/odf-operator-e2e-aws

@openshift-ci

openshift-ci Bot commented May 18, 2026

Copy link
Copy Markdown
Contributor

@iamniting: Overrode contexts on behalf of iamniting: ci/prow/odf-operator-e2e-aws

Details

In response to this:

/override ci/prow/odf-operator-e2e-aws

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.

@malayparida2000

Copy link
Copy Markdown
Contributor

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting and removed jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting labels Jul 21, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 21, 2026

Copy link
Copy Markdown

@malayparida2000: This pull request references [Jira Issue DFBUGS-6106](https://redhat.atlassian.net/browse/DFBUGS-6106), which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (odf-4.20.16) matches configured target version for branch (odf-4.20.16)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (sdurgbun@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.

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

openshift-ci Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: iamniting, malayparida2000

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

@malayparida2000

Copy link
Copy Markdown
Contributor

/override ci/prow/odf-operator-e2e-aws

@openshift-ci

openshift-ci Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

@malayparida2000: Overrode contexts on behalf of malayparida2000: ci/prow/odf-operator-e2e-aws

Details

In response to this:

/override ci/prow/odf-operator-e2e-aws

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-merge-bot
openshift-merge-bot Bot merged commit 3581b4d into red-hat-storage:release-4.20 Jul 21, 2026
16 checks passed
@openshift-ci-robot

openshift-ci-robot commented Jul 21, 2026

Copy link
Copy Markdown

@iamniting: [Jira Issue DFBUGS-6106](https://redhat.atlassian.net/browse/DFBUGS-6106): All pull requests linked via external trackers have merged:

[Jira Issue DFBUGS-6106](https://redhat.atlassian.net/browse/DFBUGS-6106) has been moved to the MODIFIED state.

Details

In response to this:

Signed-off-by: Nitin Goyal nigoyal@redhat.com

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.

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/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that the 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.

3 participants