The previous test might have made configuration changes, so call
setup_ctdb() to cause the configuration to be rewritten. This is only
really useful in local daemons tests.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
if $ctdb_test_restart_scheduled || ! cluster_is_healthy ; then
echo "Restarting CTDB (scheduled)..."
ctdb_stop_all || true # Might be restarting some daemons were shutdown
+
+ echo "Reconfiguring cluster..."
+ setup_ctdb
+
ctdb_start_all
else
# This could be made unconditional but then we might get