Run galera state on slave nodes one by one

Apply galera state in consecutive order to avoid
a race condition with database initialization.

Change-Id: I877bad38777d8469c03cee3b7e96acc875a3a72a
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
(cherry picked from commit 3bc1605a823400a80965f56ed9a502a8ce67b883)

diff --git a/mcp/config/states/openstack_ha b/mcp/config/states/openstack_ha
index 07bd6b4..77063d6 100755 (executable)
--- a/mcp/config/states/openstack_ha
+++ b/mcp/config/states/openstack_ha
@@ -25,7 +25,7 @@ salt -I 'glusterfs:server' cmd.run "gluster peer status; gluster volume status"
 salt -I 'glusterfs:client' state.sls glusterfs.client
 
 salt -I 'galera:master' state.sls galera
-salt -I 'galera:slave' state.sls galera
+salt -I 'galera:slave' state.sls galera -b 1
 salt -I 'galera:master' mysql.status | grep -A1 wsrep_cluster_size
 
 wait_for 3.0 "salt -I 'memcached:server' state.sls memcached"