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

Volume leaked if volume restore failed in restore volume step #5638

Closed
WangLe1321 opened this issue Apr 29, 2024 · 0 comments · Fixed by #5634
Closed

Volume leaked if volume restore failed in restore volume step #5638

WangLe1321 opened this issue Apr 29, 2024 · 0 comments · Fixed by #5634

Comments

@WangLe1321
Copy link
Contributor

Bug Report

What version of Kubernetes are you using?

What version of TiDB Operator are you using?

v1.5

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?

execute a volume restore, but the restore failed due to restore volume failed.

What did you expect to see?

some volumes are restored, these volumes can be cleaned by tidb-operator automatically

What did you see instead?

the restored volumes are still reserved in aws console

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant