juju bootstrap --network=UUID has no option to indicate which openstack subnet to use

[Felipe Reyes]

When using the openstack provider and spaces there is a limitation of using a single network with multiple subnets (see bug 1940334), now when there is an environment like that one there is no configuration option to bootstrap juju in a specific subnet, juju will pick up the first subnet listed by openstack.

This limitation can become a more problematic issue when that first subnet is a subnet meant to non management connectivity or simply doesn't even have a dhcp service configured.

When using maas provider it's expected the operator will take advantage of juju-mgmt-space config option to bootstrap in a specific space/subnet/vlan, but when using the openstack provider there are no spaces defined before the bootstrap process.

[Heather Lanigan (hmlanigan)]

Can you please provide the output of bootstrap with the following flags added: ` --debug --show-log`

[Felipe Reyes (freyes)]

On Fri, 2021-09-17 at 12:51 +0000, Heather Lanigan wrote:
> Can you please provide the output of bootstrap with the following flags
> added: ` --debug --show-log`

https://pastebin.canonical.com/p/pxfpwNBjnX/

[John A Meinel (jameinel)]

I think it is reasonable to implement support for '--to subnet:XXX' on openstack, which is something that we can support on other providers (currently only AWS).

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

This Medium-priority bug has not been updated in 60 days, so we're marking it Low importance. If you believe this is incorrect, please update the importance.