[2.0a3] "Add Hardware > Chassis" cannot find off-subnet chassis BMCs

[Mike Pontillo]

I tried to add a libvirt hypervisor which had an IP address not on a subnet directly attached to a cluster interface.

The UI showed me gnarly JSON error message (which I think is a separate bug) but the important part was:

    Unable to find a rack controller with access to chassis qemu+ssh://virsh@192.168.0.9/system

We recently changed the power drivers to power query every controller if we couldn't determine which was the most appropriate. We need to do something similar when adding a chassis. (it worked when I used an IP address for the BMC which was on the same subnet as the MAAS cluster.)

[Jeff Hillman (jhillman)]

This bug is still persistent in 2.2.2

Specifically adding a VMware Chassis we get "unable to find a rack controller that can contact vcenter.pizza.cf-apps.com"

Individual machines can be added with the same credentials of VMWare (hostname|username|password), but adding a chassis doesn't work.

As a workaround, in MAAS, going to the single controller and adding a 2nd interface that is on a subnet of 0.0.0.0/0 but statically assigning an IP on that interface works.

In fact, that 2nd interface isn't attached to a physical network, so it doesn't actually have connectivity, but it still allows the process to work.

[Jeff Hillman (jhillman)]

However, once we add them via chassis like that, the guests show up in MAAS, however they have no known power type and that needs to be manually updated. So it can see the machines but nothing else.