Power-down test failed because enlist test rewrote the bmc password I was using

[Julian Edwards]

Not sure what to do about this! We probably need a warning about which BMC user slot's credentials to avoid on the command line invocation for maas-test.

cmd #0027: {{{ssh -i /home/ubuntu/.config/maas-test/vm_ssh_id_rsa -o LogLevel=quiet -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no ubuntu@192.168.122.141 LC_ALL=en_US.UTF-8 ipmipower -h 10.0.0.101 -u maas -p 6rFuvt3r --stat}}}
cmd #0027 retcode: {{{0}}}
cmd #0027 stdout: {{{10.0.0.101: connection timeout}}}

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/maastest/cases.py", line 241, in test_wait_node_down
    self.fail("Node wasn't powered down after enlistment.")
  File "/usr/lib/python2.7/unittest/case.py", line 412, in fail
    raise self.failureException(msg)
AssertionError: Node wasn't powered down after enlistment.

[Julian Edwards (julian-edwards)]

In fact bizarrely, the BMC has disappeared from the network. MAAS has done something horrible to it :(