-
Notifications
You must be signed in to change notification settings - Fork 499
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
ebs br: mark backup/restore failed when job failed #5332
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #5332 +/- ##
==========================================
+ Coverage 61.61% 61.66% +0.05%
==========================================
Files 228 239 +11
Lines 28928 32712 +3784
==========================================
+ Hits 17823 20172 +2349
- Misses 9358 10689 +1331
- Partials 1747 1851 +104
|
/run-pull-e2e-kind |
/run-pull-e2e-kind-across-kubernetes |
run-pull-e2e-kind-br |
/run-pull-e2e-kind-br |
/test-pull-e2e-kind-br |
/run-pull-e2e-kind-br |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BornChanger 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 |
[LGTM Timeline notifier]Timeline:
|
New changes are detected. LGTM label has been removed. |
/run-pull-e2e-kind-br |
/run-pull-e2e-kind-br |
/run-pull-e2e-kind-br |
/run-pull-e2e-kind-br |
/run-pull-e2e-kind-br |
7 similar comments
/run-pull-e2e-kind-br |
/run-pull-e2e-kind-br |
/run-pull-e2e-kind-br |
/run-pull-e2e-kind-br |
/run-pull-e2e-kind-br |
/run-pull-e2e-kind-br |
/run-pull-e2e-kind-br |
/cherry-pick release-1.5 |
@csuzhangxc: new pull request created to branch 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 ti-community-infra/tichi repository. |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
What problem does this PR solve?
Fix the bug that when resume GC and scheduling normally, but backup failed due to pod failure.
Closes ebs br: VolumeBackup failed due to resuming GC and scheduling #5331
Fix the bug that restore pod fails due to the container being killed, but restore status doesn't set failed.
Closes ebs br: When the restore data pod fails, the volumerestore task status is not set to failed #5293
Raise error when deleting EBS snapshot failed except snapshot not found, so that we can block backup deletion when EBS snapshots aren't all be deleted.
Close When checking whether warmup has ended, if there are warmup jobs in other namespaces, it will interfere with the current results. #5405
What is changed and how does it work?
For 1 and 2, watch job status in backup/restore controller. When job is failed but backup/restore status isn't failed, set status failed.
For 3, if encounter error except not found error, return the error.
Code changes
Tests
Side effects
Related changes
Release Notes
Please refer to Release Notes Language Style Guide before writing the release note.