pingcap/tidb-operator

Volume leaked if volume restore failed in restore volume step

WangLe1321 opened this issue · 0 comments

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