Bootstrap problem on aws, 1.16.5

David Cheney david.cheney at canonical.com
Fri Feb 7 01:17:04 UTC 2014


nah, s3 has cocked up, it thinks the bucket is locked.

Just to confirm, the name of the bucket is unique and short. I've found
that bucket lengths over 20 characters are unrelable unless you use
us-east-1 -- and nobody should do that.


On Fri, Feb 7, 2014 at 11:39 AM, Andreas Hasenack <andreas at canonical.com>wrote:

> On Thu, Feb 6, 2014 at 10:35 PM, David Cheney <david.cheney at canonical.com>wrote:
>
>> Even though s3 buckets are drawn from a single global namespace, each
>> bucket has a home region. Switching to a different ec2 region, and changing
>> the name of your control bucket, will associate this new bucket with the
>> new region.
>>
>>
> Doesn't work, even tried Tokyo, which I never used.
>
> My credentials are drawn from some sort of corporate account that
> Canonical has, maybe we hit some sort of limit. I can't even delete the
> buckets I can see, I get the same conflict error (HTTP 409):
>
> $ s3cmd rb s3://juju-<somestring>
> ERROR: S3 error: 409 (OperationAborted): A conflicting conditional
> operation is currently in progress against this resource. Please try again.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20140207/c115d2ab/attachment.html>


More information about the Juju mailing list