From 188b303dd023a79bf14e586359053ba1e30d7f29 Mon Sep 17 00:00:00 2001
From: OHTAKE Tomohiro <ohtake.tomohiro@jp.fujitsu.com>
Date: Wed, 16 Mar 2016 17:58:07 +0900
Subject: [PATCH] Execute salt-call twice

---
 cluster/openstack/kubernetes-heat/fragments/run-salt.sh | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/cluster/openstack/kubernetes-heat/fragments/run-salt.sh b/cluster/openstack/kubernetes-heat/fragments/run-salt.sh
index 97d521eac74..1fe355789e1 100644
--- a/cluster/openstack/kubernetes-heat/fragments/run-salt.sh
+++ b/cluster/openstack/kubernetes-heat/fragments/run-salt.sh
@@ -45,4 +45,5 @@ sed -e 's/{{cloud_provider}}//' -i /srv/salt/kubelet/default
 # salt-call wants to start docker daemon but is unable to.
 # See <https://github.com/projectatomic/docker-storage-setup/issues/77>.
 # Run salt-call in background and make cloud-final finished.
-salt-call --local state.highstate && $$wc_notify --data-binary '{"status": "SUCCESS"}' || $$wc_notify --data-binary '{"status": "FAILURE"}' &
+# Salt-call might be unstable in some environments, execute it twice.
+salt-call --local state.highstate && salt-call --local state.highstate && $$wc_notify --data-binary '{"status": "SUCCESS"}' || $$wc_notify --data-binary '{"status": "FAILURE"}' &