pingcap/tidb-operator

ebs br: failed volumebackup can't be deleted

BornChanger opened this issue · 0 comments

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`