Run a pcs cleanup before db sync and also at the end of the deployment.
This will give processes a chance to recover in case there has been
any kind of error that would lead to a process being scored -INFINITY
due to repeated failed startup that may have been caused by load during
the deployment, or another latent issue.
Print out any services that are failed in pcs at the end of deployments.
opnfv-tht-pr: 41
Change-Id: Idf4f03cd0463a3facd0726483091ac6f1b3bf000
Signed-off-by: Michael Chapman <michapma@redhat.com>
42, congress typo
44,Fixes nova host/ip bug
43,Add support for live migration and resize
+41,Add pcs cleanup exec
echo "Undercloud IP: $UNDERCLOUD, please connect by doing 'opnfv-util undercloud'"
echo "Overcloud dashboard available at http://\$(heat output-show overcloud PublicVip | sed 's/"//g')/dashboard"
EOI
+
+if [[ "$ha_enabled" == 'True' ]]; then
+ if [ "$debug" == "TRUE" ]; then
+ echo "${blue}\nChecking pacemaker service status\n${reset}"
+ fi
+ overcloud_connect "controller0" "for i in \$(sudo pcs status | grep '^* ' | cut -d ' ' -f 2 | cut -d '_' -f 1 | uniq); do echo \"WARNING: Service: \$i not running\"; done"
+fi
}