Comment 15 for bug 1377969

I apologize about the delay in this update as I have tending to other tasks.

I spent some time on this tonight, to answer Jasons questions, I'm not entirely sure if the node is hanging 100% at this point only because I can ping the node. It does most certainly stay in a commissioning state for over 10 minutes. I can ping the IP address however the ssh daemon does not appear as if it's running, so constantly get a connection refused. Disconnecting and reconnecting the serial console does not appear to have any affect. The MAAS UI does not change in any way, the node never updates its CPU/MEMORY statistics. Even after 20 minutes it still remains in the commissioned state. smoser has giving me some suggestions to try and get more information from the console. I will try those and update the bug

Furthermore,

I removed the kernel options lines in MAAS preferences again and re-commissioned the node. During the process I took screenshots of the node in the MAAS UI. Which I can attach to this bug. In 3 minutes the node updated its CPU/MEMORY stats, and in 9 minutes switched to a READY state and powered off the node.

Interestingly enough, after the node powered off, I was not able to start my x64 avaton, after an selecting "Acquire/Start". The node failed with the following error:

----------------------------
Failed to power on node — Node could not be powered on: moonshot failed with return code 127: /bin/sh: 42: /usr/bin/ipmitool: not found Got unknown power state from ipmipower: '' /bin/sh: 42: /usr/bin/ipmitool: not found
----------------------------

Under the node -> EDIT NODE the power type had changed from "Moonshot HP ILO Manager" to "ILO4 Moonshot Chassis"
and the power address had changed from "c5n1" to "-B 0 -T 0x8a -b 7 -t 0x72 -m 0x20" \

This is wrong and perhaps a regression which might even require a separate bug. Please see screenshot ("edit_node.png")