ERROR cannot add subnet: subnet with CIDR "10.10.0.0/24" not found

[Felipe Reyes]

[Impact]

According to the documentation https://juju.is/docs/olm/network-spaces the openstack provider supports spaces, although when trying to run "juju add-space" there is an error, and for the case of "juju reload-spaces" the subnets are not pulled into juju's database.

Here it's an example of what happens when trying to create a space associated to the subnet "ironic_subnet" with the CIDR 10.10.0.0/24

$ openstack subnet list
+--------------------------------------+---------------------+--------------------------------------+--------------+
| ID | Name | Network | Subnet |
+--------------------------------------+---------------------+--------------------------------------+--------------+
| 2bb6e419-c559-4e0a-9575-4bb135349254 | freyes_admin_subnet | 27cc5fef-a820-4ddc-a426-58e2aeb98dcc | 10.5.0.0/16 |
| 6e5beb18-e5e3-4201-aa6f-bfc21a0376fb | ironic_subnet | ccf908c7-cdd9-45b5-aa35-d5de2a48b4c5 | 10.10.0.0/24 |
+--------------------------------------+---------------------+--------------------------------------+--------------+
$ juju spaces
Name Space ID Subnets
alpha 0 10.5.0.0/16

$ juju models
Controller: serverstack

Model Cloud/Region Type Status Machines Cores Units Access Last connection
controller* serverstack/serverstack openstack available 1 2 1 admin just now
default serverstack/serverstack openstack available 0 - - admin 1 hour ago

$ juju add-subnet 10.10.0.0/24 ironic-space
ERROR cannot add subnet: subnet with CIDR "10.10.0.0/24" not found
$ juju reload-spaces
$ juju spaces
Name Space ID Subnets
alpha 0 10.5.0.0/16
                 252.0.0.0/8

$ snap info juju | grep installed
installed: 3.0-beta1-acfa032 (16965) 91MB classic

Note: this behavior could be reproduced using juju 2.8, 2.9 and 3.0-beta1-acfa032 (latest/edge).

[John A Meinel (jameinel)]

This is needed for supporting Ironic for a custom space for PXE booting, etc.

The most important need from them is being able to have a bootstrapped controller that can access multiple spaces, though having dynamic runtime support for growing spaces is also useful.

[Joseph Phillips (manadart)]

At present, the OpenStack provider forces you to configure a single network to use.

Were they in the same network, this would as desired.

This scenario fails because the subnet is in a different network (ccf908c7-cdd9-45b5-aa35-d5de2a48b4c5) whereas we did discover 10.5.0.0/16 in network 27cc5fef-a820-4ddc-a426-58e2aeb98dcc.

Utilising multiple networks in OpenStack has been desired for some time, but will require specification and design work ahead of an implementation.

[Felipe Reyes (freyes)]

I was able to deploy a controller using a single network with 2 subnets, so it seems this is an issue for multi network scenarios as Joe mentioned - https://pastebin.ubuntu.com/p/879J5VMJN9/ - I still have pending to validate if this will unblock me for the Ironic testing though.

[Rodrigo Barbieri (rodrigo-barbieri2010)]

I have stumbled across the same issue. @Joseph, doesn't the link below expect that multi-network support works?

https://discourse.charmhub.io/t/openstack-multi-space-support/2672