Upgrade from 1.8 left stale devices in the UI?

[Andreas Hasenack]

I upgraded MAAS from 1.8 to 1.9, and while investigating other issues, came across this.

This is empty:
$ maas admin-vmwarestack devices list
Success.
Machine-readable output follows:
[]

But the subnet detail page in the UI shows 6 addresses allocated (see attachment).

They do show up as "reserved ip ranges", though. Not sure what that means:
$ maas admin-vmwarestack subnet reserved-ip-ranges 1
Success.
Machine-readable output follows:
[
    {
        "start": "10.245.200.1",
        "end": "10.245.200.1",
        "purpose": [
            "gateway-ip"
        ],
        "num_addresses": 1
    },
    {
        "start": "10.245.200.27",
        "end": "10.245.200.27",
        "purpose": [
            "cluster-ip"
        ],
        "num_addresses": 1
    },
    {
        "start": "10.245.201.1",
        "end": "10.245.201.255",
        "purpose": [
            "dynamic-range"
        ],
        "num_addresses": 255
    },
    {
        "start": "10.245.202.2",
        "end": "10.245.202.2",
        "purpose": [
            "assigned-ip"
        ],
        "num_addresses": 1
    },
    {
        "start": "10.245.202.3",
        "end": "10.245.202.3",
        "purpose": [
            "assigned-ip"
        ],
        "num_addresses": 1
    },
    {
        "start": "10.245.202.4",
        "end": "10.245.202.4",
        "purpose": [
            "assigned-ip"
        ],
        "num_addresses": 1
    },
    {
        "start": "10.245.202.5",
        "end": "10.245.202.5",
        "purpose": [
            "assigned-ip"
        ],
        "num_addresses": 1
    },
    {
        "start": "10.245.202.6",
        "end": "10.245.202.6",
        "purpose": [
            "assigned-ip"
        ],
        "num_addresses": 1
    },
    {
        "start": "10.245.202.7",
        "end": "10.245.202.7",
        "purpose": [
            "assigned-ip"
        ],
        "num_addresses": 1
    }
]

I'm filing this bug in a bit of a rush, sorry if it's invalid. I just didn't want to lose this data as I might have to redeploy this MAAS fresh due to other reasons.

[Mike Pontillo (mpontillo)]

My current theory (without checking the code) is that MAAS assumes that an assigned IP address is for a "Device" if it can't find a corresponding Node... and somehow you've got IP addresses assigned in MAAS which aren't associated to a known interface on a Node.

[Andres Rodriguez (andreserl)]

Hi!

We believe this is no longer an issue in the latest MAAS releases. As such, we are marking this bug report as invalid. If you believe this is still an issue, please re-open this bug report.

Thanks