Comment 11 for bug 1388860

Andrew, Awesome! I'm very excited that a good fix was found for this. Huge
Thanks.

One comment about the round robin logic. When a machine is created for the
first unit of a service, it would be nice if no AZ was selected.

From
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html#using-regions-availability-zones-launching

"When you launch your initial instances, we recommend that you accept the
default Availability Zone, because this enables us to select the best
Availability Zone for you based on system health and available capacity."

Thanks again.

On Thu, Nov 6, 2014 at 6:30 AM, Ian Booth <email address hidden> wrote:

> ** Also affects: juju-core/1.21
> Importance: Undecided
> Status: New
>
> ** Changed in: juju-core/1.21
> Importance: Undecided => High
>
> ** Changed in: juju-core/1.21
> Status: New => Fix Committed
>
> ** Changed in: juju-core/1.21
> Assignee: (unassigned) => Andrew Wilkins (axwalk)
>
> ** Changed in: juju-core
> Milestone: 1.21-beta1 => 1.22
>
> ** Changed in: juju-core/1.21
> Milestone: None => 1.21-beta1
>
> --
> 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
>