EC2 ap-southeast-2 status failures

[Tim Penhey]

On 23/04/13 00:37, David Cheney wrote:
> The usual smoking gnu is if it works inside us-east-1 (the legacy zone)
> and fails everywhere else.
> 
> Also, don't forget to make your control bucket name short, no more than
> 20 chars.

Ah... why?

> On 22/04/13 17:24, John Arbash Meinel wrote:
>> ...
>>
>>
>>> How do we move forwards with this?  It certainly looks like an AWS 
>>> issue, not a juju issue.
>>
>>> Tim
>>
>>
>> I would only mention that if this is just a difference based on zones,
>> then it is something that Juju needs to handle. If it is just a bug
>> right now, then we can defer it to AWS. (My guess is that it is
>> regional variation, though.)

Hi John,

Yes, I agree that if this is just a regional difference, then it is our
issue to sort out.  However, how do we know?

Also, I see no way of escalating this?  Do anyone know how?

If this is just a regional variation, it is a screwed up one.  In my
head I'm imagining something dumb like it parsing the timestamp
expecting a local TZ and ignoring the request because it is so far out
from what is expected... although I would be surprised.

I just don't feel like I have any clear way to move forwards with this.

Tim