not reloading spaces properly for MAAS substrate

The juju version is 2.8.11-bionic-amd64

Please supply the output for:
- "juju spaces"
- "maas <profile> subnets read"

Ah, this will be due to the fact that you will now have the same subnet, but with a different provider (MAAS) ID.

$ juju spaces
Name Space ID Subnets
alpha 0
external-space 3 103.255.54.0/24
                          199.48.155.0/24
                          31.171.208.0/24
infra-space 1 10.100.40.0/24
oam-space 2 10.100.29.0/24
                          10.100.30.0/24
                          10.100.33.0/24
                          10.100.34.0/24
                          10.102.30.0/24
                          10.108.12.0/24
                          10.108.13.0/24
                          10.108.14.0/24
                          10.108.15.0/24
                          10.108.16.0/24
                          192.168.0.0/24
                          199.48.155.0/24
undefined 4 10.116.84.0/24

$ maas admin subnets read
Success.
Machine-readable output follows:
[
    {
        "name": "eu1-seq-30",
        "description": "",
        "vlan": {
            "vid": 0,
            "mtu": 1500,
            "dhcp_on": true,
            "external_dhcp": null,
            "relay_vlan": null,
            "fabric_id": 15,
            "space": "oam-space",
            "fabric": "eu1-fabric",
            "id": 5017,
            "secondary_rack": null,
            "primary_rack": "6xhfkd",
            "name": "untagged",
            "resource_uri": "/MAAS/api/2.0/vlans/5017/"
        },
        "cidr": "10.102.30.0/24",
        "rdns_mode": 2,
        "gateway_ip": "10.102.30.1",
        "dns_servers": [],
        "allow_dns": true,
        "allow_proxy": true,
        "active_discovery": false,
        "managed": true,
        "space": "oam-space",
        "id": 13,
        "resource_uri": "/MAAS/api/2.0/subnets/13/"
    },
    {
        "name": "10.116.84.0/24",
        "description": "",
        "vlan": {
            "vid": 0,
            "mtu": 1500,
            "dhcp_on": false,
            "external_dhcp": null,
            "relay_vlan": null,
            "fabric_id": 22,
            "space": "undefined",
            "fabric": "fabric-22",
            "id": 5026,
            "secondary_rack": null,
            "primary_rack": null,
            "name": "untagged",
            "resource_uri": "/MAAS/api/2.0/vlans/5026/"
        },
        "cidr": "10.116.84.0/24",
        "rdns_mode": 2,
        "gateway_ip": null,
        "dns_servers": [],
        "allow_dns": true,
        "allow_proxy": true,
        "active_discovery": false,
        "managed": true,
        "space": "undefined",
        "id": 16,
        "resource_uri": "/MAAS/api/2.0/subnets/16/"
    },
    {
        "name": "in2-seq-13",
        "description": "",
        "vlan": {
            "vid": 0,
            "mtu": 1500,
            "dhcp_on": true,
            "external_dhcp": null,
            "relay_vlan": null,
            "fabric_id": 10,
            "space": "oam-space",
            "fabric": "in2-fabric",
            "id": 5011,
            "secondary_rack": null,
            "primary_rack": "c7qr3w",
            "name": "untagged",
            "resource_uri": "/MAAS/api/2.0/vlans/5011/"
        },
        "cidr": "10.108.13.0/24",
        "rdns_mode": 2,
        "gateway_i...

I think it is definitely worth getting them back up and running, but I don't think there is a fundamental shift that we need to spend a lot of time on.