Power Query incorrectly shows system as powered on if BMC IP address not reachable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
New
|
Undecided
|
Unassigned |
Bug Description
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-integratio
May 2 16:52:56 maas-integratio
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=
| Status=
|/ Err?=(none)
||/ Name Version Architecture Description
+++-===
ii maas 1.9.1+bzr4543-
ii maas-cli 1.9.1+bzr4543-
ii maas-cluster-
ii maas-common 1.9.1+bzr4543-
ii maas-dhcp 1.9.1+bzr4543-
ii maas-dns 1.9.1+bzr4543-
ii maas-proxy 1.9.1+bzr4543-
ii maas-region-
ii maas-region-
ii python-django-maas 1.9.1+bzr4543-
ii python-maas-client 1.9.1+bzr4543-
ii python-
This is fixed in 1.9.2