[baremetal] Shutdown nodes from previous deploy 03/66403/1
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Sun, 13 Jan 2019 17:49:07 +0000 (18:49 +0100)
committerAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Tue, 15 Jan 2019 13:52:10 +0000 (13:52 +0000)
commit6be6f921ef58007804641a6defe7536af03e6a97
treee4e1b56ede6b7f4825c7cee4c1841210d1c94e5c
parent9ca1c4f8c3d5639d46c99b5fa3a9f06b485f0fb7
[baremetal] Shutdown nodes from previous deploy

When noha scenarios are scheduled on the same CI POD currently
running a previously deployed HA scenario, one baremetal node
might remain unused (kvm03), connect to the new Salt master and
interfere with the deployment.

To prevent that, shutdown all baremetal nodes at the begining of the
deployment.

Change-Id: Ia9bad8b5d8348433cefac9aa76eca0de664f187d
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
(cherry picked from commit 267bd35d4b7656a7eb0236fa04acbbaba76f5da3)
mcp/scripts/lib.sh