ctdb-tests: Fix description of NFS tickle test

Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>

diff --git a/ctdb/tests/complex/31_nfs_tickle.sh b/ctdb/tests/complex/31_nfs_tickle.sh
index fbb30c14cc7f7c3aaec3a52a184ca252982be4b7..c82d31dda1b569e437532382196efca8654fd3f8 100755 (executable)
--- a/ctdb/tests/complex/31_nfs_tickle.sh
+++ b/ctdb/tests/complex/31_nfs_tickle.sh
@@ -7,8 +7,8 @@ Verify that NFS connections are monitored and that NFS tickles are sent.
 
 We create a connection to the NFS server on a node and confirm that
 this connection is registered in the nfs-tickles/ subdirectory in
-shared storage.  Then disable the relevant NFS server node and ensure
-that it send an appropriate reset packet.
+shared storage.  Then kill ctdbd on the relevant NFS server node and
+ensure that the takeover node sends an appropriate reset packet.
 
 Prerequisites:
 
@@ -21,21 +21,10 @@ Prerequisites:
 
 * Cluster nodes must be listening on the NFS TCP port (2049).
 
-Steps:
-
-1. Verify that the cluster is healthy.
-2. Connect from the current host (test client) to TCP port 2049 using
-   the public address of a cluster node.
-3. Determine the source socket used for the connection.
-4. Ensure that CTDB records the source socket details in the nfs-tickles
-   directory on shared storage.
-5. Disable the node that the connection has been made to.
-6. Verify that a TCP tickle (a reset packet) is sent to the test client.
-
 Expected results:
 
-* CTDB should correctly record the socket and should send a reset
-  packet when the node is disabled.
+* CTDB should correctly record the socket and on failover the takeover
+  node should send a reset packet.
 EOF
 }