Power Query incorrectly shows system as powered on if BMC IP address not reachable

[Larry Michel]

Moving a roadrunner system between test and production environment means having to change the BMC address as it shares eth0 with the OS. I am expecting that Power Query will fail on origin MAAS server where I have marked node as broken since system is no longer on that maas network. However, the query continues to show the power as ON. If I click on check power state, it thinks for a while then returns to Power ON state.

Since system is showed as PowerON, then MAAS UI allows me to attempt to power it off. This is the error I get:

May 2 16:52:36 maas-integration-september maas.power: [INFO] Changing power state (off) of node: bailey (node-df9e41f4-ee2a-11e5-af8d-00163e35cf93)
May 2 16:52:56 maas-integration-september maas.drivers.power.ipmi: [WARNING] Failed to change the boot order to PXE 10.244.234.97: /usr/sbin/ipmi-chassis-config: connection timeout

Timing out on the BMC IP address should put the power indicator in MAAS UI in error state as it does for incorrect credentials.

$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-================================-================================-============-===============================================================================
ii maas 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server all-in-one metapackage
ii maas-cli 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS command line API tool
ii maas-cluster-controller 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server cluster controller
ii maas-common 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server common files
ii maas-dhcp 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS DHCP server
ii maas-dns 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS DNS server
ii maas-proxy 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS Caching Proxy
ii maas-region-controller 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server complete region controller
ii maas-region-controller-min 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS Server minimum region controller
ii python-django-maas 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server Django web framework
ii python-maas-client 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS python API client
ii python-maas-provisioningserver 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server provisioning libraries

[Andres Rodriguez (andreserl)]

This is fixed in 1.9.2