[19:25] <bread555> Does anyone know where to disable the maas-test functionality? Due to my config, I don't really need remote power up/off so just need to prevent maas from not installing due to hardward configurations
[22:20] <qhartman> I have a MAAS isntallation running, but nodes are failing to be commissioned
[22:21] <qhartman> When I get to the commissioning step, they power up (WOL) and seem t o start commissioning, but then shut down right as the process seems to get going. Googling has failed me.
[22:21] <qhartman> Any suggestions for where to look on the server for some logs that point me in the right direction?
[22:22] <qhartman> I get a string of "Success" messages and then what looks like some service start status messages, then shutdown. Not sure what happens last, it shuts down too quick to really read
[22:26] <qhartman> Oh, it's also noteworthy that it complains aboutno ipmi user slots being available right before the string of "success" messages. Since it got past that I thought it might not be a fatal error
[22:26] <qhartman> but I suppose some power control stuff might be happening incorrectly as a result and that might be what's killing the nodes before the install can really go
[22:49] <qhartman> ok, another one I've found is that I need to change the interface that etherwake uses to turn up nodes
[22:50] <qhartman> I've found /etc/maas/templates/ether_wake.template and made the appropriate change there (added "-i eth1"), but how do I make that change live? MAAS seems to be ignoring it.
[23:07] <qhartman> turns out I needed to add an ssh key to the MAAS system, to enable the start button, and that's when the installation actually happens
[23:08] <qhartman> That's not called out in the docs anywhere that I've seen, fwiw