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.

Sign up for GitHub

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

Jump to bottom

OCPBUGS-21217: CVE-2023-39325 ose-cluster-samples-operator-container:golang: net/http, x/net/http2: rapid stream resets can cause excessive work (CVE-2023-44487) #539

Merged
merged 1 commit into from Apr 4, 2024
Merged

OCPBUGS-21217: CVE-2023-39325 ose-cluster-samples-operator-container:golang: net/http, x/net/http2: rapid stream resets can cause excessive work (CVE-2023-44487) #539

merged 1 commit into from Apr 4, 2024

Conversation

fbm3307
Copy link
Contributor

@fbm3307 fbm3307 commented Apr 3, 2024

No description provided.

@fbm3307
OCPBUGS-21217: CVE-2023-39325 ose-cluster-samples-operator-container:…
9f4f343 
… golang: net/http, x/net/http2: rapid stream resets can cause excessive work (CVE-2023-44487)

Signed-off-by: Feny Mehta <fbm3307@gmail.com>
@openshift-ci-robot openshift-ci-robot added 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 3, 2024
@openshift-ci-robot
Copy link
Contributor

@fbm3307: This pull request references Jira Issue OCPBUGS-21217, which is invalid:

  • expected Jira Issue OCPBUGS-21217 to depend on a bug targeting a version in 4.15.0, 4.15.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.

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.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 3, 2024
@fbm3307
Copy link
Contributor Author

fbm3307 commented Apr 3, 2024

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@fbm3307: This pull request references Jira Issue OCPBUGS-21217, which is invalid:

  • expected dependent Jira Issue OCPBUGS-22034 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.

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.

@fbm3307
Copy link
Contributor Author

fbm3307 commented Apr 3, 2024

/label cherry-pick-approved

@fbm3307
Copy link
Contributor Author

fbm3307 commented Apr 3, 2024

/label backport-risk-assessed

@openshift-ci openshift-ci bot added cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. labels Apr 3, 2024
@fbm3307
Copy link
Contributor Author

fbm3307 commented Apr 3, 2024

/test okd-images

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Apr 3, 2024

@fbm3307: 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/okd-scos-e2e-aws-operator 9f4f343 link false /test okd-scos-e2e-aws-operator
ci/prow/okd-scos-e2e-aws-ovn-jenkins 9f4f343 link false /test okd-scos-e2e-aws-ovn-jenkins
ci/prow/okd-scos-e2e-aws-ovn-upgrade 9f4f343 link false /test okd-scos-e2e-aws-ovn-upgrade
ci/prow/okd-scos-e2e-aws-ovn 9f4f343 link false /test okd-scos-e2e-aws-ovn
ci/prow/okd-e2e-aws-ovn-image-ecosystem 9f4f343 link false /test okd-e2e-aws-ovn-image-ecosystem
ci/prow/okd-e2e-aws-ovn 9f4f343 link false /test okd-e2e-aws-ovn
ci/prow/okd-e2e-aws-ovn-builds 9f4f343 link false /test okd-e2e-aws-ovn-builds
ci/prow/okd-scos-e2e-aws-ovn-builds 9f4f343 link false /test okd-scos-e2e-aws-ovn-builds
ci/prow/okd-e2e-aws-ovn-upgrade 9f4f343 link false /test okd-e2e-aws-ovn-upgrade
ci/prow/okd-scos-e2e-aws-ovn-image-ecosystem 9f4f343 link false /test okd-scos-e2e-aws-ovn-image-ecosystem
ci/prow/okd-e2e-aws-ovn-jenkins 9f4f343 link false /test okd-e2e-aws-ovn-jenkins

Full PR test history. Your PR dashboard.

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/test-infra repository. I understand the commands that are listed here.

dperaza4dustbit
dperaza4dustbit approved these changes Apr 3, 2024
View reviewed changes
Copy link
Contributor

@dperaza4dustbit dperaza4dustbit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 3, 2024
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Apr 3, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dperaza4dustbit, fbm3307

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:
  • OWNERS [dperaza4dustbit,fbm3307]

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

@fbm3307
Copy link
Contributor Author

fbm3307 commented Apr 3, 2024

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@fbm3307: This pull request references Jira Issue OCPBUGS-21217, which is invalid:

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

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

@fbm3307
Copy link
Contributor Author

fbm3307 commented Apr 4, 2024

/jira refresh

@openshift-ci-robot 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 Apr 4, 2024
@openshift-ci-robot
Copy link
Contributor

@fbm3307: This pull request references Jira Issue OCPBUGS-21217, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-22034 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-22034 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
  • bug has dependents

Requesting review from QA contact:
/cc @jitendar-singh

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-bot openshift-merge-bot bot merged commit 61a3465 into openshift:release-4.14 Apr 4, 2024
16 of 27 checks passed
@openshift-ci-robot
Copy link
Contributor

@fbm3307: Jira Issue OCPBUGS-21217: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-21217 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.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-cluster-samples-operator-container-v4.14.0-202404040208.p0.g61a3465.assembly.stream.el8 for distgit ose-cluster-samples-operator.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dperaza4dustbit dperaza4dustbit dperaza4dustbit approved these changes

@adambkaplan adambkaplan Awaiting requested review from adambkaplan

@gabemontero gabemontero Awaiting requested review from gabemontero

@jitendar-singh jitendar-singh Awaiting requested review from jitendar-singh

Assignees

@dperaza4dustbit dperaza4dustbit

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a 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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
4 participants
@fbm3307 @openshift-ci-robot @openshift-bot @dperaza4dustbit