Test suite: Fix debug code for unexpectedly unhealthy cluster.

The debug code should run "ctdb status" on a cluster node, not on the
test client.

Signed-off-by: Martin Schwenke <martin@meltin.net>

diff --git a/tests/scripts/ctdb_test_functions.bash b/tests/scripts/ctdb_test_functions.bash
index 38324d7a9ef8595fde486e2f253637a18246f710..8fd6141ecff43c0f41a9b6a3fdfe0b104693b2e2 100644 (file)
--- a/tests/scripts/ctdb_test_functions.bash
+++ b/tests/scripts/ctdb_test_functions.bash
@@ -342,7 +342,7 @@ cluster_is_healthy ()
        if ! ${ctdb_test_restart_scheduled:-false} ; then
            echo "DEBUG:"
            local i
-           for i in "ctdb status" "onnode -q 0 onnode all ctdb scriptstatus" ; do
+           for i in "onnode -q 0 ctdb status" "onnode -q 0 onnode all ctdb scriptstatus" ; do
                echo "$i"
                $i || true
            done
@@ -529,7 +529,7 @@ tcpdump_wait ()
     if ! wait_until 30 tcpdump_check ; then
        echo "DEBUG:"
        local i
-       for i in "ctdb status" "netstat -tanp" "tcpdump -n -e -r $tcpdump_filename" ; do
+       for i in "onnode -q 0 ctdb status" "netstat -tanp" "tcpdump -n -e -r $tcpdump_filename" ; do
            echo "$i"
            $i || true
        done