incubator-deltacloud-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "" <>
Subject Issue with S3 API and creating buckets that already exist (and owned by you)
Date Fri, 04 Feb 2011 19:12:30 GMT

Michal reported an issue with the aws s3 (ec2) in teambox

I recently found that when you create a new bucket in EC2 and you use 
name which is already taken by another bucket it will always return 
'true' instead of throwing an exception. Seems like it's an another bug 
in aws gem, because when I checked create_bucket in EC2 driver I got 
true in every case.
As a workaround we could check if bucket exists and if so, we can throw 
our BackendError.

I've spent the best part of today trying to debug this; in the end the 
problem is neither our code nor the aws gem. The issue is with the S3 
API. See

*Create a bucket that already exists, but you do not own:

===> you get an error from S3 (BucketAlreadyExists) since bucket names 
are used as FQDNs (e.g.

*Create a bucket that already exists, that you do own AND you set a 
location other than the default eu-east-1 (by including a 
CreateBucketConfiguration and LocationConstraint elements in your 
request body)

====> you get an error from S3 (BucketAlreadyOwnedByYou).

*Create a bucket that already exists, that you do own but don't specify 
a location (so it gets put into eu-east-1)

====> no error, the bucket gets 're-created' which basically means its 
'creation time' gets updated (but otherwise nothing else, your blobs 
remain intact). THIS IS THE SCENARIO Michal was facing.


Since this is an issue with the provider API theres not much we can do. 
There's no 'bucket_exists' call; the only solution i can see is to get a 
list of all bucket names and check these for the bucket you are about to 
create, but I don't know if thats acceptable?


View raw message