Comment 3 for bug 1890527

OK, If you like me land on this bug, there is a workaround. This apparently happens only if you have individual VMs registered under MASS, but their respective KVM host is not.

If it is a KVM host with no VMs or if you don't mind MASS taking over existing VMs (be careful here since it is going to try to commission any existing VMs in), go ahead and add the KVM host under KVM > Virsh.

This resolved the issue for me.

In case you add a KVM host with existing VMs, just abort commissioning for those VMs and turn them back on. Let them sit under the "New" section of MAAS. I know it is not very clean, but hey.