moved subnets do not get updated by reload-spaces

[Peter Matulis]

Juju's notion of spaces does not correspond to what is in MAAS.

What I did:

https://paste.ubuntu.com/26536992/

What is in the MAAS database:

https://paste.ubuntu.com/26537201/

Software:

juju 2.3.2-xenial-amd64
maas 2.3.0-6434-gd354690-0ubuntu1

[John A Meinel (jameinel)]

I thought we had a bug already for this, but the only one I could find was https://bugs.launchpad.net/juju/+bug/1705767.

There are a few things you can do in MAAS that Juju does not currently track appropriately.
a) Rename space (we consider the name of a space its primary identifier, and thus renaming it just looks like a different space, we could track it differently as MAAS has a *different* primary key)
b) Move a subnet from one space to another (we'd like to support this generally, but have always been concerned because if you have deployed units that are using a given subnet, moving a subnet to another space has fairly profound impact to bindings and promises to charmers/operators.)
c) changing the definition of a subnet (192.168.0.1/22 becomes 192.168.0.1/24). Again we consider the CIDR to be the primary identifier, so those look like 2 different subnets to us.
d) We don't handle subnets that overlap very well. See (c) above which should be conflicting, you shouldn't be able to have both.
e) multiple networks that are not connected having the same subnet

[John A Meinel (jameinel)]

If you rebootstrap, the new juju will see the spaces that MAAS has after the update. 'reload-spaces' currently only really supports adding new spaces or new subnets.

[Florian Guitton (f-guitton)]

Hello,

I hope everybody is all right !

Do we have an ETA on this ?
We are currently in the process of updating our IP ranges and this is severely breaking Juju.

Best wishes,