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-43187: runc library bump to 1.1.12 #440

Open
wants to merge 1 commit into
base: release-4.12
Choose a base branch
from
Open

OCPBUGS-43187: runc library bump to 1.1.12 #440

wants to merge 1 commit into from

Conversation

prabhapa
Copy link
Contributor

runc golang package is bumped from 1.1.3 to 1.1.12 to fix the CVE CVE-2024-21626

@prabhapa
OCPBUGS-43187: runc library bump to 1.1.12
b2735bb 
runc golang package is bumped from 1.1.3 to 1.1.12 to fix the CVE CVE-2024-21626
@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 Jan 28, 2025
@openshift-ci-robot
Copy link
Contributor

@prabhapa: This pull request references Jira Issue OCPBUGS-43187, 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-43191 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.

In response to this:

runc golang package is bumped from 1.1.3 to 1.1.12 to fix the CVE CVE-2024-21626

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 Jan 28, 2025
@prabhapa
Copy link
Contributor Author

/label backport-risk-assessed
/label cherry-pick-approved

@openshift-ci openshift-ci bot added 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. labels Feb 20, 2025
@prabhapa
Copy link
Contributor Author

/retest

@prabhapa
Copy link
Contributor Author

/test e2e-aws-ovn-builds

1 similar comment
@prabhapa
Copy link
Contributor Author

/test e2e-aws-ovn-builds

@prabhapa
Copy link
Contributor Author

/override ci/prow/e2e-aws-ovn-builds
this failure is a known issue and backport is in progress hance overriding.

@prabhapa
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@prabhapa: This pull request references Jira Issue OCPBUGS-43187, which is invalid:

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

@de1987
Copy link

de1987 commented Feb 20, 2025

/lgtm

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 20, 2025

@prabhapa: Overrode contexts on behalf of prabhapa: ci/prow/e2e-aws-ovn-builds

In response to this:

/override ci/prow/e2e-aws-ovn-builds
this failure is a known issue and backport is in progress hance overriding.

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-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 20, 2025

@prabhapa: 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/e2e-aws-ovn-proxy b2735bb link false /test e2e-aws-ovn-proxy
ci/prow/e2e-aws-ovn-builds b2735bb link true /test e2e-aws-ovn-builds
ci/prow/security b2735bb link false /test security
ci/prow/e2e-aws-ovn-builds-techpreview b2735bb link false /test e2e-aws-ovn-builds-techpreview

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

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

openshift-ci bot commented Feb 20, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: de1987, prabhapa

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

1 similar comment
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Feb 20, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: de1987, prabhapa

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

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

@de1987 de1987 de1987 approved these changes

@Moebasim Moebasim Awaiting requested review from Moebasim

@sayan-biswas sayan-biswas Awaiting requested review from sayan-biswas

Assignees

@de1987 de1987

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/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. 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.
3 participants
@prabhapa @openshift-ci-robot @de1987