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.15] OCPNODE-2101: add kube-rbac-proxy-crio toleration change #28637

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #28636

/assign rphillips

@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 6, 2024

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: OCPNODE-2099

In response to this:

This is an automated cherry-pick of #28636

/assign rphillips

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 deads2k and mfojtik March 6, 2024 01:30
Copy link
Contributor

openshift-ci bot commented Mar 6, 2024

@openshift-cherrypick-robot: 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-etcd-recovery bac6d0f link false /test e2e-aws-etcd-recovery
ci/prow/e2e-aws-ovn-upgrade bac6d0f link false /test e2e-aws-ovn-upgrade
ci/prow/e2e-aws-ovn-single-node bac6d0f link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-single-node-upgrade bac6d0f link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-single-node-serial bac6d0f link false /test e2e-aws-ovn-single-node-serial

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.

@rphillips
Copy link
Contributor

rphillips commented Mar 6, 2024

/retitle [release-4.15] OCPNODE-2101: add kube-rbac-proxy-crio toleration change

@openshift-ci openshift-ci bot changed the title [release-4.15] OCPNODE-2099: add kube-rbac-proxy-crio toleration change [release-4.15] OCPNODE-2101: add kube-rbac-proxy-crio toleration change Mar 6, 2024
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 6, 2024
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 6, 2024

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

In response to this:

This is an automated cherry-pick of #28636

/assign rphillips

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.

@rphillips
Copy link
Contributor

/retest-required

@deads2k deads2k added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 8, 2024
@deads2k
Copy link
Contributor

deads2k commented Mar 8, 2024

/lgtm

@deads2k deads2k 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 Mar 8, 2024
Copy link
Contributor

openshift-ci bot commented Mar 8, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, 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

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 8, 2024
@deads2k deads2k added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Mar 8, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit d68c509 into openshift:release-4.15 Mar 8, 2024
18 of 23 checks passed
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-tests-container-v4.15.0-202403082308.p0.gd68c509.assembly.stream.el8 for distgit openshift-enterprise-tests.
All builds following this will include this PR.

@rphillips
Copy link
Contributor

/cherry-pick release-4.14

@openshift-cherrypick-robot
Copy link
Author

@rphillips: new pull request created: #28647

In response to this:

/cherry-pick release-4.14

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.

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.

None yet