Skip to content
This repository has been archived by the owner on Dec 3, 2024. It is now read-only.

Delete bucketAccess failed because credentialsSecret is not exist #153

Open
FanZhang526 opened this issue Oct 10, 2024 · 0 comments
Open

Comments

@FanZhang526
Copy link

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:

  • 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:
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant