I have a MAAS cluster controller with two NIC (eth0 - 22.214.171.124/24 - connected to public network and p1p1 - 192.168.0.0/24 - used for private MAAS nodes). I use 5 physical machines HP compaq 6000 Pro. When I turn on one of these machines, it correctly does PXE boot from the MAAS cluster controller and in the MAAS console it is shown as "declared". There is a warning icon next to the hostname with error:
This node does not have a power type set and MAAS will be unable to control it. Click 'Edit node' and set one.
Also, it shows 0 CPU, Memory and disk space.
When, I update the power type to "Wake-on-LAN" with the correct MAC and save, I'm not able to commission the node. It does not turn on the machine and hangs on the "commissioning" status. I checked time is correctly set on the node (check in BIOS).
The WOL with the node works just fine, i.e., I can turn it on using:
wakeonlan -i 192.168.0.255 00:23:24:0e:0d:e7
from the MAAS cluster controller. I have to specify the
-i 192.168.0.255 since the default
255.255.255.255 does not do anything.
If I turn it on manually (e.g. using
wakeonlan) it eventually goes into
ready state and correctly detects CPU, Memory and disk space. Again, if I try to start the, it wont do anything, but if I power it on manually, it works just fine.
It seems that the problem is related to having two NICs - the magic packet is only sent over the eth1 (even though the cluster is correctly configured indicating p1p1 as the managed interface) which is incorrect (sudo tcpdump -i eth1 port 9 -vvvv -s0 -n). Submitted a bug https://bugs.launchpad.net/maas/+bug/1343317