Upgrade from 1.8 to 1.9 lost connected macs in all but one network

[Andreas Hasenack]

We had many networks defined in our MAAS 1.8 system, and all networks had all our nodes connected to them. In other words, list-connected-macs <network> would return one mac per node for all <network>.

After upgrading that to 1.9, just one network had results for list-connected-macs. It also so happens that this network in particular is the managed one, all the others were not managed.

[Mike Pontillo (mpontillo)]

It looks like this is because we are joining the MACs to the Subnet via the IP address table. If (for whatever reason) the MACs in question don't have IP addresses, it looks like you might hit this issue.

Can you execute "sudo maas-region-admin dbshell" on the region, and then run this query:

https://paste.ubuntu.com/14591836/

I'll paste the query here as well:

SELECT
    subnet.name,
    vlan.vid,
    fabric.name,
    iface.mac_address
FROM
    maasserver_subnet subnet
    LEFT OUTER JOIN maasserver_vlan vlan
        on subnet.vlan_id = vlan.id
    LEFT OUTER JOIN maasserver_fabric fabric
        on vlan.fabric_id = fabric.id
    LEFT OUTER JOIN maasserver_interface iface
        on iface.vlan_id = vlan.id
ORDER BY subnet.name, vlan.vid, iface.mac_address;

[Andreas Hasenack (ahasenack)]

I get what looks like the correct output. Many macs listed for each network.

[Mike Pontillo (mpontillo)]

Note that this is only an issue for 1.9 and 1.10; in MAAS 2.0 we are dropping support for the (legacy) networks API endpoint.

[Mike Pontillo (mpontillo)]

Thanks. I believe this is the fix:

https://paste.ubuntu.com/14591973/

As a workaround, that patch could be applied to /usr/lib/python2.7/dist-packages/maasserver/api/networks.py until an official fix is released.

[Andreas Hasenack (ahasenack)]

That worked for me