subnet directive gives misleading error when subnet doesn't exist

[Chris Scheper]

When using bootstrap to deploy controller to non-standard subnet 172.16.128.0/22 but mistakenly enter the incorrect subnet or netmask the error displays a "unknown placement directive" as opposed to "unknown subnet".

example: subnet 172.16.128.0/22

incorrect input "172.17.128.0/22" or "172.16.128.0/20"

$ juju bootstrap aws/us-east-1 my_controller --to subnet=172.16.128.0/20
ERROR failed to bootstrap model: cannot start bootstrap instance: unknown placement directive: subnet=172.16.128.0/20

changing the netmask from 20 to 22 makes the command work correctly.

Thanks,
-Chris

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 2 years, so we're marking it Low importance. If you believe this is incorrect, please update the importance.