Project

General

Profile

Actions

Bug #3128

closed

Obsync doesn't appear to handle permanent redirect with specified endpoint from Amazon

Added by JuanJose Galvez over 11 years ago. Updated over 11 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Support
Tags:
Backport:
Regression:
Severity:
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

It seems that accessing the bucket from http://s3.amazonaws.com/mikesbackup3or results in a PermanentRedirect error. The results also includes a URL that should be used for access:

<Endpoint>mikesbackup3or.s3.amazonaws.com</Endpoint>

-------------
Full details from DHO follow:

Given proper credentials set in environment variables:

/usr/bin/obsync -V -c --no-preserve-acls --src-type=s3 --src-host=s3.amazonaws.com --src-bucket=mikesbackup3or --dst-type=s3 --dst-host=objects.dreamhost.com --dst-bucket=mikesbackup3or
result: 256
Timeout: no
Stdout: SOURCE: s3.amazonaws.com, mikesbackup3or, None (s3)

Stderr:

2012-09-10 01:30:43,113 stdout [INFO]:Enabling verbose boto logging.
2012-09-10 01:30:43,114 stdout [DEBUG]:path=/mikesbackup3or/
2012-09-10 01:30:43,114 stdout [DEBUG]:auth_path=/mikesbackup3or/
2012-09-10 01:30:43,114 stdout [DEBUG]:path=/mikesbackup3or/?&max-keys=0
2012-09-10 01:30:43,114 stdout [DEBUG]:auth_path=/mikesbackup3or/?&max-keys=0
2012-09-10 01:30:43,114 stdout [DEBUG]:Method: GET
2012-09-10 01:30:43,114 stdout [DEBUG]:Path: /mikesbackup3or/?&max-keys=0
2012-09-10 01:30:43,114 stdout [DEBUG]:Data:
2012-09-10 01:30:43,114 stdout [DEBUG]:Headers: {}
2012-09-10 01:30:43,114 stdout [DEBUG]:Host: s3.amazonaws.com
2012-09-10 01:30:43,114 stdout [DEBUG]:establishing HTTP connection: kwargs={}
2012-09-10 01:30:43,114 stdout [DEBUG]:Token: None
2012-09-10 01:30:43,115 stdout [DEBUG]:StringToSign:
GET

Mon, 10 Sep 2012 01:30:43 GMT
/mikesbackup3or/
2012-09-10 01:30:43,268 stdout [DEBUG]:
<Error><Code>PermanentRedirect</Code><Message>The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint.</Message><RequestId>FA3D669CBE1B50C7</RequestId><Bucket>mikesbackup3or<HostId>BWSGDzXgZLb0W4tislLF9L1kKXZ2ifgYtdfsVXZ2OJCrCFrh6IAbeIvU50Ywjtxr</HostId><Endpoint>mikesbackup3or.s3.amazonaws.com</Endpoint></Error> File "/usr/bin/obsync", line 1135, in <module>
prefix=opts.src_prefix, path=opts.src_path)
File "/usr/bin/obsync", line 550, in make_store
return S3Store(kwargs['host'], kwargs['bucket'], kwargs['prefix'], create, akey, skey, is_secure)
File "/usr/bin/obsync", line 658, in init
(host, self.bucket_name))
File "/usr/bin/obsync", line 128, in init
ObsyncException.__init__(self, "permanent", e)
File "/usr/bin/obsync", line 107, in init
self.tb = "".join(traceback.format_stack())

s3.amazonaws.com: no such bucket as mikesbackup3or
ERROR TYPE: permanent, ORIGIN: source

Actions #1

Updated by Sage Weil over 11 years ago

  • Status changed from New to Fix Under Review

wip-obsync

Actions #2

Updated by Sage Weil over 11 years ago

  • Status changed from Fix Under Review to Resolved
Actions

Also available in: Atom PDF