juju bootstrap to a particular subnet

[John Meinel]

It should still be available for AWS. I think I saw a case where you might
get that error just when it can't find the subnet you asked for (so
'subnet=' is known, but the 172.32.* couldn't be found).
I'm not positive about it, but I do still see the subnet matching code in
place.

John
=:->


On Mon, Jun 25, 2018 at 11:42 PM, chris <prpht9 at gmail.com> wrote:

> Hello everyone,
>
>   In looking through the docs I was unable to find a way to deploy a
> controller to a specific subnet.  I found some old bug reports where there
> was possibly a --to directive added to facilitate this back in 2.2.
> However, this is what happens when I use it...
>
> juju bootstrap --config vpc-id=vpc-XXXXXXXX --credential=cred_name
> aws/region controller_name --to subnet=172.32.X.X/20
> ERROR failed to bootstrap model: cannot start bootstrap instance: unknown
> placement directive: subnet=172.32.X.X/20
>
>   Is this directive still available?  Has it changed?
>
> Thanks,
> -Chris
>
> --
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20180702/66bb25d8/attachment.html>