pingcap / pingcap/tidb-operator
Deleting volume backup during its running can cause snapshot leakage [restore for 5087]
Open
@BornChanger is already working on this.
Since Oct 25, 2024.
area/ebs-br
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Bug Report
What version of Kubernetes are you using?
What version of TiDB Operator are you using?
wangle1321/tidb-operator:202305261650
What storage classes exist in the Kubernetes cluster and what are used for PD/TiKV pods?
gp3
What's the status of the TiDB cluster pods?
noraml
What did you do?
- create cluster(cross k8s)
- create volume backup
- delete volume backup when it is running status
What did you expect to see?
- bucket is deleted
- snapshot is deleted
What did you see instead?
- snapshot is not be deleted
- there is only 2 volume backup(each has 6 2T snapshot,total 12 2T snapshot), but has more than 12 snapshot in aws account
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.