-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide better error descriptions for CSI-S3 access and connection failures #249
Comments
I would like to take this @srikumar003 /assign |
i am seeing the invalid endpoint errors when running in Kind. i have tried a bunch of variants for the how does one go about diagnosing/debugging/fixing these kinds of issues? |
@ashutosh887 apologies for not responding and thanks for taking on this issue! |
Thanks @srikumar003 |
I have the same issue and cannot understand what's wrong:
The CRD is the next: apiVersion: com.ie.ibm.hpsys/v1alpha1
kind: Dataset
metadata:
name: mm-db-dump
spec:
local:
type: "COS" # Cloud Object Storage
secret-name: "s3-dump-secret"
#secret-namespace: "{SECRET_NAMESPACE}" #optional if the secret is in the same ns as dataset
endpoint: "http://rgw-slow-dev01.ti.local"
bucket: "mm-db-dump"
readonly: "false" # default is false
provision: "false" # DLF will allocate bucket on the COS if it doesn't exist [Default: false]
#region: "" #it can be empty |
The issue was that #90 (comment) |
Issue:
Currently, CSI-S3 emits this error string in the logs most of the time:
failed to initialize S3 client: Endpoint: does not follow ip address or domain name standards
. However, the root causes of this error can be different e.g. #160 #90 The dataset is left pending.Requirements:
Provide an error log message corresponding to the root cause and use it to populate the status field of the Dataset.
The text was updated successfully, but these errors were encountered: