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
When the tenant specifies the bucket to create, any subsequent request should not mask the error as an info here and should check the bucket exists before attempting to create it.
Current Behavior
The operator will continually try to create bucket, and subsequent to the initial creation, it will log an error wrapped as info suggesting it was already successfully created. This creates two problems:
Noisy logs
Generating false positives in Grafana dashboard since attempt to create and already existing bucket generates a 400 error generated here.
Possible Solution
Check the bucket exists before attempting to create it to avoid API 400 error and noisy logs.
Steps to Reproduce (for bugs)
In the tenant values.yaml, specify a bucket to create.
Context
Regression
Your Environment
Version used (minio-operator):
Environment name and version (e.g. kubernetes v1.17.2):
Server type and version:
Operating System and version (uname -a):
Link to your deployment file:
The text was updated successfully, but these errors were encountered:
Expected Behavior
When the tenant specifies the bucket to create, any subsequent request should not mask the error as an info here and should check the bucket exists before attempting to create it.
Current Behavior
The operator will continually try to create bucket, and subsequent to the initial creation, it will log an error wrapped as info suggesting it was already successfully created. This creates two problems:
Possible Solution
Check the bucket exists before attempting to create it to avoid API 400 error and noisy logs.
Steps to Reproduce (for bugs)
In the tenant values.yaml, specify a bucket to create.
Context
Regression
Your Environment
minio-operator
):uname -a
):The text was updated successfully, but these errors were encountered: