From e05cafe19b5d4257b8de569caedf1b8273fc5a89 Mon Sep 17 00:00:00 2001 From: Pranav Salunke Date: Wed, 6 May 2015 14:43:21 +0200 Subject: [PATCH] Changes exit status for heat_network unit test If the test fails, it should exit the script not the cluster. Just reporting this error and gracefully exiting the script should be sufficient. My reasons for this are: * The tests are not completely reliable to say if the cluster is broken for sure. * The tests are not meant to fix the issues with the cluster, it could be a packaging issue or bug in the product. Our aim is not to catch them. * If there is a problem with heat, the other servies are still running fine. And the cluster is still usable. Change-Id: I246bd3144189eba69a64ad545e6fe123e310595e --- labs/scripts/ubuntu/setup_heat_network.sh | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/labs/scripts/ubuntu/setup_heat_network.sh b/labs/scripts/ubuntu/setup_heat_network.sh index 70647ad5..2c3578b9 100755 --- a/labs/scripts/ubuntu/setup_heat_network.sh +++ b/labs/scripts/ubuntu/setup_heat_network.sh @@ -68,7 +68,9 @@ until node_ssh controller-mgmt "$AUTH; heat stack-list" 2>/dev/null | grep "CREA echo node_ssh controller-mgmt "$AUTH; heat stack-list" echo "Heat stack creation failed. Exiting." - exit 1 + echo "[Warning]: Please debug heat services on the + controller and network node. Heat may not work." + exit 0 else sleep 1 echo -n "."