Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DFBUGS-1245: build: update x/net version to fix CVE #116

Merged

Conversation

subhamkrai
Copy link
Contributor

No description provided.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 10, 2025

@subhamkrai: This pull request references [Jira Issue DFBUGS-1245](https://issues.redhat.com//browse/DFBUGS-1245), which is invalid:

  • expected the bug to target either version "odf-4.17.3." or "openshift-odf-4.17.3.", but it targets "odf-4.17.5" 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.

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.

@subhamkrai
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 13, 2025

@subhamkrai: This pull request references [Jira Issue DFBUGS-1245](https://issues.redhat.com//browse/DFBUGS-1245), which is valid. The bug has been moved to the POST state.

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

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.

@sp98
Copy link
Contributor

sp98 commented Feb 13, 2025

/lgtm

Copy link

openshift-ci bot commented Feb 13, 2025

@sp98: changing LGTM is restricted to collaborators

In response to this:

/lgtm

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.

@nb-ohad
Copy link

nb-ohad commented Feb 13, 2025

/lgtm

Copy link

openshift-ci bot commented Feb 13, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nb-ohad, sp98, subhamkrai

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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

@sunilheggodu
Copy link

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 13, 2025

@sunilheggodu: This pull request references [Jira Issue DFBUGS-1245](https://issues.redhat.com//browse/DFBUGS-1245), which is valid.

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

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.

@sunilheggodu sunilheggodu added jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting jira/invalid-bug Indicates that the referenced jira bug is invalid for the branch this PR is targeting and removed jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting labels Feb 13, 2025
@sunilheggodu
Copy link

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 13, 2025

@sunilheggodu: This pull request references [Jira Issue DFBUGS-1245](https://issues.redhat.com//browse/DFBUGS-1245), which is valid.

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

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.

@sunilheggodu sunilheggodu 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 Feb 13, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 94385bb into red-hat-storage:release-4.17 Feb 13, 2025
1 check passed
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 13, 2025

@subhamkrai: [Jira Issue DFBUGS-1245](https://issues.redhat.com//browse/DFBUGS-1245): All pull requests linked via external trackers have merged:

[Jira Issue DFBUGS-1245](https://issues.redhat.com//browse/DFBUGS-1245) has been moved to the MODIFIED state.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved jira/valid-bug Indicates that the referenced jira bug is valid for the branch this PR is targeting lgtm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants