glusterfs/tests/bugs/bug-1112559.t
Joseph Fernandes c7251ebfe8 glusterd/regression: Temp fix for spurious err
As discussed in the mail,
Disabling the checking of snap brick status until
the investigation is done on the port bind issue.

Change-Id: I8854cee050de1b7f843e3d40631b6cb61fd8583e
BUG: 1112559
Signed-off-by: Joseph Fernandes <josferna@redhat.com>
Reviewed-on: http://review.gluster.org/8259
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Vijay Bellur <vbellur@redhat.com>
2014-07-10 11:12:00 -07:00

62 lines
1.5 KiB
Bash
Executable File

#!/bin/bash
. $(dirname $0)/../include.rc
. $(dirname $0)/../cluster.rc
. $(dirname $0)/../volume.rc
. $(dirname $0)/../snapshot.rc
function check_peers {
$CLI_1 peer status | grep 'Peer in Cluster (Connected)' | wc -l
}
function check_snaps_status {
$CLI_1 snapshot status | grep 'Snap Name : ' | wc -l
}
function check_snaps_bricks_health {
$CLI_1 snapshot status | grep 'Brick Running : Yes' | wc -l
}
SNAP_COMMAND_TIMEOUT=40
NUMBER_OF_BRICKS=2
cleanup;
TEST verify_lvm_version
TEST launch_cluster 3
TEST setup_lvm 3
TEST $CLI_1 peer probe $H2
EXPECT_WITHIN $PROBE_TIMEOUT 1 peer_count
TEST $CLI_1 volume create $V0 $H1:$L1 $H2:$L2
TEST $CLI_1 volume start $V0
#Create snapshot and add a peer together
$CLI_1 snapshot create ${V0}_snap1 ${V0} &
PID_1=$!
$CLI_1 peer probe $H3
wait $PID_1
#Snapshot should be created and in the snaplist
TEST snapshot_exists 1 ${V0}_snap1
#Not being paranoid! Just checking for the status of the snapshot
#During the testing of the bug the snapshot would list but actually
#not be created.Therefore check for health of the snapshot
EXPECT_WITHIN $SNAP_COMMAND_TIMEOUT 1 check_snaps_status
#Disabling the checking of snap brick status , Will continue investigation
#on the failure of the snapbrick port bind issue.
#EXPECT_WITHIN $SNAP_COMMAND_TIMEOUT $NUMBER_OF_BRICKS check_snaps_bricks_health
#check if the peer is added successfully
EXPECT_WITHIN $PROBE_TIMEOUT 2 peer_count
TEST $CLI_1 snapshot delete ${V0}_snap1
cleanup;