Martin Schwenke 7cff3ed12c ctdb-tests: Use a local "ctdb shutdown" command to avoid a race ... When "ctdb shutdown" is run with -n <N> it does not wait for the node <N>'s ctdbd to go down but exits immediately. This means that the local_daemons.sh shutdown command can find the PID file still present and then attempt the shutdown, but the daemon can have exited between the check and the shutdown. Although the test waits until the node is disconnected, the transport is taken down just before the exit, so this does not guarantee the daemon has exited. A local shutdown command (no -n <N>) waits until the socket disconnects and this happens *after* the PID file is gone, so this is safe to use with the local_daemons.sh shutdown command. Signed-off-by: Martin Schwenke <martin@meltin.net> Reviewed-by: Amitay Isaacs <amitay@gmail.com> Autobuild-User(master): Amitay Isaacs <amitay@samba.org> Autobuild-Date(master): Mon Mar 2 10:39:28 UTC 2020 on sn-devel-184		2020-03-02 10:39:28 +00:00
..
database	ctdb-tests: Rationalise node stop/start/restart	2020-02-18 02:56:38 +00:00
failover	ctdb-tests: Add function ctdb_test_skip_on_cluster()	2019-10-04 09:41:28 +00:00
simple	ctdb-tests: Use a local "ctdb shutdown" command to avoid a race	2020-03-02 10:39:28 +00:00