Comment 1 for bug 1747998

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