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 delete bucketAccess, bucketAccess Controller will delete the related credentialsSecret.
When credentialsSecret is deleted before bucketAccess is deleted, an error message is displayed indicating that the secret object cannot be found. So, the bucketAccess can not be deleted successfully.
What you expected to happen:
When credentialsSecret is deleted before bucketAccess is deleted, the bucketAccess can be deleted successfully.
How to reproduce this bug (as minimally and precisely as possible):
1、create a bucketClaim.
2、create a bucketAccess by using this bucketClaim.
3、delete the credentialsSecret of this bucketAccess.
4、delete this bucketAccess
Anything else relevant for this bug report?:
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:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug Report
What happened:
When delete bucketAccess, bucketAccess Controller will delete the related credentialsSecret.
When credentialsSecret is deleted before bucketAccess is deleted, an error message is displayed indicating that the secret object cannot be found. So, the bucketAccess can not be deleted successfully.
What you expected to happen:
When credentialsSecret is deleted before bucketAccess is deleted, the bucketAccess can be deleted successfully.
How to reproduce this bug (as minimally and precisely as possible):
1、create a bucketClaim.
2、create a bucketAccess by using this bucketClaim.
3、delete the credentialsSecret of this bucketAccess.
4、delete this bucketAccess
Anything else relevant for this bug report?:
Environment:
kubectl version
), please list client and server:cat /etc/os-release
):uname -a
):The text was updated successfully, but these errors were encountered: