volumesnapshotcontent-bound-protection finalizer is not removed although volumesnapshot-being-deleted annotation is set #1112
Labels
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
(this is probably a follow-up to #248)
What happened:
I wanted to delete a namespace, which also triggered the deletion of the volume snapshots in this namespace. However, the volumesnapshotcontent resources were never removed. Only after manually removing the volumesnapshotcontent-bound-protection finalizer, all resources could be removed. Additionally, no events were logged that might lead to an error in the backend.
What you expected to happen:
The volumesnapshots and the respective volumesnapshotcontent resources are deleted successfully. Or, if any error occurs, the resources have events attached to them.
How to reproduce it:
Delete a volumesnapshot.
Anything else we need to know?:
Our environment is based on VMware Tanzu
Environment:
kubectl version
):uname -a
):Linux int-default-dkgsc-66488c4554x88fdb-9p5sc 4.19.307-6.ph3 #1-photon SMP Sat Apr 6 14:24:47 UTC 2024 x86_64 GNU/Linux
The text was updated successfully, but these errors were encountered: