In some scenarios, the log print is abnormal #150
Description
Bug Report
What happened:
When creating bucketClaim with incorrect config, then the bucket has been created but is in an abnormal state. The COSI sidecar component continuously prints error events. However, after the bucket is deleted successfully, the cosi sidecar component keeps printing the event.
What you expected to happen:
After the bucket is deleted successfully, the cosi sidecar component do not print the error event.
How to reproduce this bug (as minimally and precisely as possible):
1、create a bucketclaim with incorrect config, the bucket has been created but is in an abnormal state.
2、viewing COSI Sidecar container logs.
3、delete this bucketclaim (bucket also deleted).
4、viewing COSI Sidecar container logs again, it is found that error events are continuously printed.
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: