Comment 7 for bug 1388860

I did not think I had any VPC, but you prompted me to check and indeed I
had one. I've since deleted it. Hopefully I'll never see this message again.

Still, the behavior from juju seemed to place new machines into the same AZ
every time a new machine was added. This meant no new machines were usable.
It would be nice to document that juju either does or does not choose an AZ
or under what conditions it chooses an AZ.

On Wed, Nov 5, 2014 at 11:06 PM, John A Meinel <email address hidden>
wrote:

> This sounds like a case of someone using default-vpc and it has a default
> subnet on most availability zones (a-d) but does *not* have a default
> subnet on us-east-1e.
> Switching to eu-west-1 means you are using a different set of configured
> networks (either not in VPC or with a different set of subnets configured).
>
> We are looking at configuring VPC on Amazon in this cycle, but I don't
> believe that bigger solution is reasonable for 1.21.
>
> Its possible we could just skip zones that don't have a subnet
> configured?
>
> This sort of failure sounds very specific to a given user's account and
> how their EC2 environment is configured, as such it will be hard for us
> to reproduce and fix. If it fails reasonably reliably for you, we can
> try to determine some workarounds and work with you to see if it fixes
> things.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1388860
>
> Title:
> ec2 says agent-state-info: 'cannot run instances: No default
> subnet for availability zone: ''us-east-1e''. (InvalidInput)'
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1388860/+subscriptions
>