Using maas 0.1+bzr1243+dfsg-0ubuntu3, installed this morning.
I additionally imported Quantal images by editing /etc/maas/import_pxe_files and adding quantal to RELEASES before running sudo maas-import-pxe-files. Then I set "Default distro series used for commissioning" to Quantal using the Web UI.
Enlisting a node does not set power parameters. The console output suggests that power parameters were not sent (empty string).
Commissioning a node also does not set power parameters. I see this during commissioning:
Setting up freeipmi-tools (1.1.5-3ubuntu2) ...
Processing triggers for libc-bin ...
ldconfig deferred processing now taking place
Traceback (most recent call last):
File "/tmp/part-001.iniXie/bin/maas-signal", line 262, in <module>
main()
File "/tmp/part-001.iniXie/bin/maas-signal", line 227, in main
power_pass=args.power_parms.split(",")[1],
IndexError: list index out of range
Success
Success
Success
Finished, powering off.
This does not occur using Precise ephemerals. Note that for Precise to work on highbank, I have to add ppa:maas-maintainers/dailybuilds to the enlistment userdata, since highbank detection requires the maas-enlist SRU which hasn't landed yet. As expected without the latest maas-enlist, power parameters only get set in commissioning, not in enlistment.
The cause for this is that ipmi-locate output between precise and quantal is different on highbank. In fact, on quantal ipmi-locate appears to no longer work.
A workaround Scott and I have discussed is to look for /dev/ipmi0 after the existing logic detects nothing. This appears to be sufficient on highbank, and doesn't give me a false positive on my (non-IPMI) machine.