BR: confused wrong region error
Please answer these questions before submitting your issue. Thanks!
-
What did you do? If possible, provide a recipe for reproducing the error. br restore from an non-exist region on S3
-
What did you expect to see? incorrect region error info
-
What did you see instead? Error: Bucket tools-uw2 is not accessible: MissingEndpoint: 'Endpoint' configuration is required for this service
This error info is from S3 service. But users might think if --s3.endpoint is required.
- What version of BR and TiDB/TiKV/PD are you using?
$ ./bin/br -V
Release Version: v5.0.0-master
Git Commit Hash: fa66494bcf9395016b7847fecddd7e83478af27a
Git Branch: master
Go Version: go1.16.2
UTC Build Time: 2021-03-28 02:36:16
Race Enabled: false
-
Operation logs
- Please upload
br.logfor BR if possible - Please upload
tidb-lightning.logfor TiDB-Lightning if possible - Please upload
tikv-importer.logfrom TiKV-Importer if possible - Other interesting logs
- Please upload
-
Configuration of the cluster and the task
-
tidb-lightning.tomlfor TiDB-Lightning if possible -
tikv-importer.tomlfor TiKV-Importer if possible -
topology.ymlif deployed by TiUP
-
-
Screenshot/exported-PDF of Grafana dashboard or metrics' graph in Prometheus if possible
/label severity/minor
@cyliu0: The label(s) severity/minor cannot be applied. These labels are supported: Hacktoberfest, duplicate, good first issue, invalid, needs-cherry-pick-3.1, needs-cherry-pick-4.0, needs-cherry-pick-5.0, needs-cherry-pick-5.0-rc, question, release-blocker, wontfix.
In response to this:
/label severity/minor
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.