[June 2025] - The bucketClaim deleted, related bucketAccess is not deleted #79
Description
Bug Report
What happened:
When a bucketClaim is deleted, the associated bucketAccess is not deleted. There is only one associated bucketAccess, and this bucketAccess fails to be provisioned.
What you expected to happen:
When bucketClaim is deleted, the related bucketAccess is deleted regardless of whether bucketAccess is successfully provisioned.
How to reproduce this bug (as minimally and precisely as possible):
1、bucketClaim is successfully created.
2、create a bucketAccess for this bucketClaim. The bucketAccess fails and keeps retrying.
3、delete bucketClaim.
Anything else relevant for this bug report?:
1、related code is in line 214~216 of file pkg/bucket/bucket_controller.go.
2、when associated bucketAccess is not provisioned successfully, finalizers "cosi.objectstorage.k8s.io/bucketaccess-bucket-protection" on bucket does not exist.
Environment:
- Kubernetes version (use
kubectl version), please list client and server: - Sidecar version (provide the release tag or commit hash):
- Provisoner name and version (provide the release tag or commit hash):
- Cloud provider or hardware configuration:
- OS (e.g:
cat /etc/os-release): - Kernel (e.g.
uname -a): - Install tools:
- Network plugin and version (if this is a network-related bug):
- Others: