In MAAS versions earlier than 1.9 I could use MAAS to autodiscover and configure IPMI settings like this:
* enlist systems
* set power type to "IPMI" without credentials
* set node to "commission"
* power on manually
* MAAS would fill out IPMI details automatically and was able to control power once that happened
I tried the same approach in 1.9 but it did not work. When I set node with incomplete IPMI settings to "Commissioning" it immediately goes into error state and even if I power on manually commissioning does not happen.
Ability for MAAS to autoconfigure IPMI was very useful and saved a lot of time can you add it back?
un maas <none> <none> (no description available)
ii maas-cli 1.9.1+bzr4543-0ubuntu2~trusty1 all MAAS command line API tool
un maas-cluster-controller <none> <none> (no description available)
ii maas-common 1.9.1+bzr4543-0ubuntu2~trusty1 all MAAS server common files
un maas-dhcp <none> <none> (no description available)
ii maas-dns 1.9.1+bzr4543-0ubuntu2~trusty1 all MAAS DNS server
ii maas-proxy 1.9.1+bzr4543-0ubuntu2~trusty1 all MAAS Caching Proxy
ii maas-region-controller 1.9.1+bzr4543-0ubuntu2~trusty1 all MAAS server complete region controller
ii maas-region-controller-min 1.9.1+bzr4543-0ubuntu2~trusty1 all MAAS Server minimum region controller
ii python-django-maas 1.9.1+bzr4543-0ubuntu2~trusty1 all MAAS server Django web framework
ii python-maas-client 1.9.1+bzr4543-0ubuntu2~trusty1 all MAAS python API client
ii python-maas-provisioningserver 1.9.1+bzr4543-0ubuntu2~trusty1 all MAAS server provisioning libraries
Hi Jacek,
Both the auto-enlistment feature and commissioning automatically auto-configure IPMI. If you had to enlist a system, and it resulted in not having IPMI auto-configured, but it would configure it on commissioning, then I'd say there's something wrong there.
Can you attach console logs of either enlistment or commissioning to see what's going on?