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

[release-4.16] USHIFT-3481: Add explicit crun default runtime configuration for crio #3477

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #3475

/assign pacevedom

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 12, 2024

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: USHIFT-3477

In response to this:

This is an automated cherry-pick of #3475

/assign pacevedom

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 requested review from jerpeter1 and pliurh June 12, 2024 13:43
@pacevedom
Copy link
Contributor

pacevedom commented Jun 12, 2024

/retitle [release-4.16] USHIFT-3481: Add explicit crun default runtime configuration for crio

@openshift-ci openshift-ci bot changed the title [release-4.16] USHIFT-3477: Add explicit crun default runtime configuration for crio [release-4.16] USHIFT-3481: Add explicit crun default runtime configuration for crio Jun 12, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 12, 2024

@openshift-cherrypick-robot: This pull request references USHIFT-3481 which is a valid jira issue.

In response to this:

This is an automated cherry-pick of #3475

/assign pacevedom

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 12, 2024
Copy link
Contributor

openshift-ci bot commented Jun 12, 2024

@openshift-cherrypick-robot: all tests passed!

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.

@pacevedom
Copy link
Contributor

/jira refresh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 12, 2024

@pacevedom: This pull request references USHIFT-3481 which is a valid jira issue.

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.

@pacevedom
Copy link
Contributor

/label backport-risk-assessed

@pacevedom
Copy link
Contributor

/cc @jogeo

@openshift-ci openshift-ci bot requested a review from jogeo June 12, 2024 15:09
@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jun 12, 2024
@jerpeter1
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jun 12, 2024
@jogeo
Copy link
Contributor

jogeo commented Jun 12, 2024

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jun 12, 2024
@kwilczynski
Copy link
Member

/approve
/lgtm

Copy link
Contributor

openshift-ci bot commented Jun 12, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jerpeter1, kwilczynski, openshift-cherrypick-robot

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

@jogeo
Copy link
Contributor

jogeo commented Jun 12, 2024

/label jira/valid-bug

Copy link
Contributor

openshift-ci bot commented Jun 12, 2024

@jogeo: Can not set label jira/valid-bug: Must be member in one of these teams: []

In response to this:

/label jira/valid-bug

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.

@pacevedom
Copy link
Contributor

/label jira/valid-bug

@openshift-ci openshift-ci bot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Jun 12, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 04e0e81 into openshift:release-4.16 Jun 12, 2024
7 checks passed
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. 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
Development

Successfully merging this pull request may close these issues.

7 participants