andy/glusterfs
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

test: Check till probe timeout, for conf change sync across glusterd

Browse Source 
Currently the test case changed here, checks for the peer count to
be 1 until probe timeout and then checks for the changed
configuration, if it has been synced.

The peer count is not a gurantee that the configuration is also
in sync, hence changing this test case to check for the conf
update till probe timeout, by which time it should be in sync
(or at least that is our tolerance), and the test case deemed
as passing.

Change-Id: I4b1560979cfde3bd3bd691852d7d3a63e253bcf2
BUG: 1181203
Signed-off-by: Shyam <srangana@redhat.com>
Reviewed-on: http://review.gluster.org/9498
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
Reviewed-by: Krishnan Parthasarathi <kparthas@redhat.com>
Tested-by: Krishnan Parthasarathi <kparthas@redhat.com>
This commit is contained in:
Shyam 2015-01-27 10:42:54 -05:00 committed by Krishnan Parthasarathi
parent ee3d92e83c
commit 2f640b3f3c
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
tests/bugs/glusterd/bug-1104642.t
View File

@ -42,6 +42,6 @@ TEST $glusterd_2
#Verify whether the value has been synced
EXPECT '80' get_value 'cluster.server-quorum-ratio' 1
EXPECT_WITHIN $PROBE_TIMEOUT '1' peer_count
EXPECT '80' get_value 'cluster.server-quorum-ratio' 2
EXPECT_WITHIN $PROBE_TIMEOUT '80' get_value 'cluster.server-quorum-ratio' 2
cleanup;