Skip to content
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

Impossible to store backups in AWS S3 eu-south-2 (Spain) region #302

Closed
yajo opened this issue Feb 20, 2023 · 3 comments
Closed

Impossible to store backups in AWS S3 eu-south-2 (Spain) region #302

yajo opened this issue Feb 20, 2023 · 3 comments

Comments

@yajo
Copy link

yajo commented Feb 20, 2023

For some weird reason, when setting region=eu-south-2 (because the bucket is there), the operator will fail to connect to the buckets, with this error:

INFO[2023/02/20 10:48:16] invoking set s3 service client                insecure-tls-skip-verify=false s3-accessKey=MYACCESSKEY s3-bucketName=mybucket s3-endpoint=s3-accesspoint.dualstack.eu-south-2.amazonaws.com s3-endpoint-ca= s3-folder= s3-region=eu-south-2
ERRO[2023/02/20 10:48:16] error syncing 'default-location-recurring-backup': handler backups: failed to check if s3 bucket [mybucket] exists, error: 400 Bad Request, requeuing 

Workaround: Move the bucket to eu-west-3 and reconfigure the operator.

@moduon MT-2305

@yajo yajo changed the title Impossible to store backups in AWS S3 eu-south-2 region Impossible to store backups in AWS S3 eu-south-2 (Spain) region Feb 20, 2023
@MKlimuszka
Copy link

We will investigate further. No initial leads after reviewing what is reported here.

@jbiers
Copy link
Member

jbiers commented Oct 18, 2024

We could not reproduce this issue. In our tests, changing from a us-east-1 to a eu-south-2 bucket did not result in any errors and backups could be saved successfully. This is likely an issue with the cloud setup and not with Rancher/BRO.

@mallardduck
Copy link
Member

Since our team cannot replicate this issue based on the region as described we'll close this out. As mentioned by @jbiers - it's more likely there are other configuration issues or incompatible settings in use on the bucket in that region. If you identify what those settings are please follow up and let us know.

@mallardduck mallardduck closed this as not planned Won't fix, can't repro, duplicate, stale Oct 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants