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

ebs br: failed volumebackup can't be deleted #5503

Closed
BornChanger opened this issue Jan 5, 2024 · 0 comments · Fixed by #5492
Closed

ebs br: failed volumebackup can't be deleted #5503

BornChanger opened this issue Jan 5, 2024 · 0 comments · Fixed by #5492
Labels
area/ebs-br type/bug Something isn't working

Comments

@BornChanger
Copy link
Contributor

Bug Report

What version of Kubernetes are you using?

What version of TiDB Operator are you using?

What storage classes exist in the Kubernetes cluster and what are used for PD/TiKV pods?

What's the status of the TiDB cluster pods?

What did you do?

Delete to a failed volumebackup, whose data plane fails at snapshot generation, and the backup meta file is not created.

What did you expect to see?
The failed volumebackup delete succeed.

What did you see instead?

E0103 10:37:11.151656       9 clean.go:89] read metadata file /backupmeta failed, err: open /backupmeta: no such file or directory, a manual check or delete action required.
E0103 10:37:11.151681       9 clean.go:69] For backup xxx clean, failed to clean backup: open /backupmeta: no such file or directory
E0103 10:37:11.151687       9 manager.go:88] delete backup xxx for cluster xxx failure
E0103 10:37:11.151692       9 manager.go:102] clean cluster xxx backup s3://xxx failed, err: open /backupmeta: no such file or directory
error: open /backupmeta: no such file or directory`
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ebs-br type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant