mirror of
https://github.com/samba-team/samba.git
synced 2025-01-11 05:18:09 +03:00
37c26a9590
Separate cluster startup from test initialisation for tests that start the cluster with customised configuration. In these cases the result of the cluster startup is actually the point of the test. Additionally, pubips.013.failover_noop.sh claims to have completed test initialisation twice, which just seems wrong. The result is: * ctdb_test_init() takes one option (-n) to indicate when it should not configure/start the cluster * New function ctdb_nodes_start_custom() accepts options for special cluster configuration, only operates on local daemons and triggers a test failure rather than a test error on failure. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com>
17 lines
262 B
Bash
Executable File
17 lines
262 B
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
# Check that CTDB operates correctly if there are 0 event scripts
|
|
|
|
|
|
. "${TEST_SCRIPTS_DIR}/integration.bash"
|
|
|
|
set -e
|
|
|
|
ctdb_test_skip_on_cluster
|
|
|
|
ctdb_test_init -n
|
|
|
|
ctdb_nodes_start_custom --no-event-scripts
|
|
|
|
echo "Good, that seems to work!"
|