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

In some scenarios, the log print is abnormal #150

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

In some scenarios, the log print is abnormal #150

FanZhang526 opened this issue Oct 10, 2024 · 0 comments

Comments

@FanZhang526
Copy link

FanZhang526 commented Oct 10, 2024

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:
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