-
Notifications
You must be signed in to change notification settings - Fork 125
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
NO-JIRA: remove cluster-backup pod #1182
NO-JIRA: remove cluster-backup pod #1182
Conversation
Signed-off-by: lan.tian <lance5890@163.com>
Hi @lance5890. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
/retest |
2 similar comments
/retest |
/retest |
/retest-required |
/retest |
7 similar comments
/retest |
/retest |
/retest |
/retest |
/retest |
/retest |
/retest |
prow/e2e-gcp-qe-no-capabilities is being made optional |
/retest-required |
Thanks @lance5890! We have to wait until the nightly builds are catching up and the label requirements are lifted, but otherwise /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lance5890, tjungblu 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 |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
/retitle NO-JIRA: remove cluster-backup pod |
@lance5890: This pull request explicitly references no jira issue. 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. |
/jira refresh |
@tjungblu: This pull request explicitly references no jira issue. 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. |
@lance5890 it will likely retest for a while, I'll keep an eye out to get this merged soonish |
/override ci/prow/e2e-operator-fips |
@tjungblu: Overrode contexts on behalf of tjungblu: ci/prow/e2e-operator-fips 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 kubernetes/test-infra repository. |
/override ci/prow/e2e-agnostic-ovn-upgrade unrelated failures |
@tjungblu: Overrode contexts on behalf of tjungblu: ci/prow/e2e-agnostic-ovn-upgrade, ci/prow/e2e-aws-ovn-single-node, ci/prow/e2e-gcp-qe-no-capabilities 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 kubernetes/test-infra repository. |
@lance5890: 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/test-infra repository. I understand the commands that are listed here. |
Thanks @lance5890 and sorry for the long wait |
[ART PR BUILD NOTIFIER] This PR has been included in build cluster-etcd-operator-container-v4.17.0-202404302014.p0.gcb78ee2.assembly.stream.el9 for distgit cluster-etcd-operator. |
As the UpgradeBackupController has been removed by the PR #1129
the cluster-backup-pod has no effect anymore