Test suite: Ask CTDB about CIFS tickles registered for the actual test node.

This failed when node 0 had no public IPs because we would always run
"ctdb gettickles" on node.  We now ask node 0 for the tickles on the
test node.

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

diff --git a/tests/complex/32_cifs_tickle.sh b/tests/complex/32_cifs_tickle.sh
index 94b28617d9a6cbff062b721399161a74a5127309..407f35c4793a65c07d1544beafcff07b05d55a77 100755 (executable)
--- a/tests/complex/32_cifs_tickle.sh
+++ b/tests/complex/32_cifs_tickle.sh
@@ -74,7 +74,7 @@ echo "Source socket is $src_socket"
 # CTDB faster than it takes us to wait for netstat to register the
 # connection and then use onnode below to ask CTDB about it.
 
-try_command_on_node -v 0 ctdb gettickles $test_ip
+try_command_on_node -v 0 ctdb gettickles $test_ip -n $test_node
 
 if [ "${out/SRC: ${src_socket} /}" != "$out" ] ; then
     echo "GOOD: CIFS connection tracked OK by CTDB."
@@ -85,7 +85,7 @@ fi
 
 tcptickle_sniff_start $src_socket "${test_ip}:${test_port}"
 
-echo "Disabling node $test_node"
+echo "Disabling node $test_node"r
 try_command_on_node 1 $CTDB disable -n $test_node
 onnode 0 $CTDB_TEST_WRAPPER wait_until_node_has_status $test_node disabled