-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
br: fix getting region failure with other s3 compatible storage (#39653) #39693
br: fix getting region failure with other s3 compatible storage (#39653) #39693
Conversation
Signed-off-by: WangLe1321 <wangle1321@163.com>
Signed-off-by: WangLe1321 <wangle1321@163.com>
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/run-check_dev_2 |
1 similar comment
/run-check_dev_2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/LGTM |
LGTM |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: fd611b3
|
This is an automated cherry-pick of #39653
Signed-off-by: WangLe1321 wangle1321@163.com
What problem does this PR solve?
Issue Number: close #39648
Problem Summary:
full backup get 403 error with message "failed to get region of bucket xxx" when use other s3 compatible storage.
What is changed and how it works?
modify not to use path style addressing when use other s3 compatible storage to get region.
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.