Comment 7 for bug 1789426

After a while, the other machines were marked failed releasing, because they timed out. That means that power management failure/traceback may be blocking other operations from continuing to be able to perform:

==> /var/log/maas/maas.log <==
Aug 28 20:40:43 maas00 maas.power: [error] Error changing power state (off) of node: node03 (ncyhd6)
Aug 28 20:40:43 maas00 maas.node: [info] node03: Status transition from RELEASING to FAILED_RELEASING
Aug 28 20:40:43 maas00 maas.node: [error] node03: Marking node failed: Timed out

==> /var/log/maas/rackd.log <==
2018-08-28 20:40:43 provisioningserver.rpc.power: [info] node04: Power could not be set to off; timed out.

==> /var/log/maas/maas.log <==
Aug 28 20:40:43 maas00 maas.power: [error] Error changing power state (off) of node: node04 (mnwpg8)

==> /var/log/maas/rackd.log <==
2018-08-28 20:40:43 provisioningserver.rpc.power: [info] node02: Power could not be set to off; timed out.

==> /var/log/maas/maas.log <==
Aug 28 20:40:43 maas00 maas.power: [error] Error changing power state (off) of node: node02 (6y8g6m)
Aug 28 20:40:43 maas00 maas.node: [info] node02: Status transition from RELEASING to FAILED_RELEASING
Aug 28 20:40:43 maas00 maas.node: [info] node04: Status transition from RELEASING to FAILED_RELEASING
Aug 28 20:40:43 maas00 maas.node: [error] node02: Marking node failed: Timed out
Aug 28 20:40:43 maas00 maas.node: [error] node04: Marking node failed: Timed out

==> /var/log/maas/rackd.log <==
2018-08-28 20:40:43 provisioningserver.rpc.power: [info] node05: Power could not be set to off; timed out.

==> /var/log/maas/maas.log <==
Aug 28 20:40:43 maas00 maas.power: [error] Error changing power state (off) of node: node05 (d4wqsc)
Aug 28 20:40:43 maas00 maas.node: [info] node05: Status transition from RELEASING to FAILED_RELEASING
Aug 28 20:40:43 maas00 maas.node: [error] node05: Marking node failed: Timed out