mirror of
https://github.com/samba-team/samba.git
synced 2025-01-14 19:24:43 +03:00
96b3517356
cluster_is_healthy() is now run locally in tests and internally causes _cluster_is_healthy() to be run on node 0. When it detects that the cluster is unhealthy and $ctdb_test_restart_scheduled is not true, debug information is printed. This replaces the previous use of $CTDB_TEST_CLEANING_UP. To avoid spurious debug on expected restarts, added scheduled restarts to several tests. Signed-off-by: Martin Schwenke <martin@meltin.net> (This used to be ctdb commit ee7caae3a55a64fb50cd28fa2fd4663c5dd83b4f)
40 lines
877 B
Bash
Executable File
40 lines
877 B
Bash
Executable File
#!/bin/bash
|
|
|
|
test_info()
|
|
{
|
|
cat <<EOF
|
|
Verify that the ctdb_persistent test succeeds for unsafe persistent writes.
|
|
|
|
Prerequisites:
|
|
|
|
* An active CTDB cluster with at least 2 active nodes.
|
|
|
|
Steps:
|
|
|
|
1. Verify that the status on all of the ctdb nodes is 'OK'.
|
|
2. Run two copies of ctdb_persistent on each node with a 30 second
|
|
timeout and with the --unsafe-writes option.
|
|
3. Ensure that all ctdb_persistent processes complete successfully.
|
|
|
|
Expected results:
|
|
|
|
* ctdb_persistent tests unsafe persistent writes without error.
|
|
EOF
|
|
}
|
|
|
|
. ctdb_test_functions.bash
|
|
|
|
ctdb_test_init "$@"
|
|
|
|
set -e
|
|
|
|
cluster_is_healthy
|
|
|
|
try_command_on_node 0 "$CTDB listnodes"
|
|
num_nodes=$(echo "$out" | wc -l)
|
|
|
|
t="$CTDB_TEST_WRAPPER $VALGRIND ctdb_persistent --unsafe-writes --timelimit=30"
|
|
|
|
echo "Running ctdb_persistent --unsafe-writes on all $num_nodes nodes."
|
|
try_command_on_node -v -pq all "$t & $t"
|