summaryrefslogtreecommitdiffstats
path: root/lib/overcloud-deploy-functions.sh
diff options
context:
space:
mode:
authorDan Radez <dradez@redhat.com>2017-05-17 16:29:11 -0400
committerDan Radez <dradez@redhat.com>2017-05-17 16:41:10 -0400
commit3dd07ba7905005ceb49c00cca9046853e8eebc2f (patch)
tree211aa4f5bdd511fa68a5c26123c829f1c1624024 /lib/overcloud-deploy-functions.sh
parent3fe04fbdbfdbf7d362c45e615e8526285670e8c9 (diff)
Add VBMC double check
Sometimes the VBMC devices don't all start and stay started This checks that they are all running before starting a deployment Change-Id: I3c69d31549798a5837475d10b8a365bb0e5c9a3d Signed-off-by: Dan Radez <dradez@redhat.com>
Diffstat (limited to 'lib/overcloud-deploy-functions.sh')
-rwxr-xr-xlib/overcloud-deploy-functions.sh7
1 files changed, 5 insertions, 2 deletions
diff --git a/lib/overcloud-deploy-functions.sh b/lib/overcloud-deploy-functions.sh
index 1c5e4d0a..52b2f783 100755
--- a/lib/overcloud-deploy-functions.sh
+++ b/lib/overcloud-deploy-functions.sh
@@ -330,8 +330,11 @@ EOI
DEPLOY_OPTIONS+=" --control-flavor control --compute-flavor compute"
if [[ "$virtual" == "TRUE" ]]; then
DEPLOY_OPTIONS+=" -e virtual-environment.yaml"
- # double check the status of the vbmc devices
- # TODO add some validation logic here
+ echo 'Ensuring Virtual BMC device status'
+ for i in $(vbmc list | grep down | awk '{ print $2}'); do
+ vbmc start $i
+ sleep 5
+ done
vbmc list
fi