You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 3, 2024. It is now read-only.
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:
The text was updated successfully, but these errors were encountered:
FanZhang526
changed the title
The bucketClaim deleted, related bucketaccess is not deleted
The bucketClaim deleted, related bucketAccess is not deleted
Oct 10, 2024
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
kubectl version
), please list client and server:cat /etc/os-release
):uname -a
):The text was updated successfully, but these errors were encountered: