diff options
| author | Gaurav Kumar Garg <garg.gaurav52@gmail.com> | 2016-02-15 10:48:18 +0530 |
|---|---|---|
| committer | Atin Mukherjee <amukherj@redhat.com> | 2016-02-22 04:01:11 -0800 |
| commit | 62db11fa017004aa6cb1d91ec6b0117ac3e96a13 (patch) | |
| tree | a9da3a06d239ef51bb5df8b2ec644bd38f475a7c /tests | |
| parent | f02dc88786afea06e6b064a724803c82a0af90ba (diff) | |
glusterd: volume should not start when server quorum is not met
Currently when server quorum is not met then upon executing
# gluster volume start [force] command its starting the volume.
With this patch if server side quorum is not met then it will
prevent starting of the volume.
Change-Id: I39734b2dcf8e90c3c68bf2762d8350aecc82cc38
BUG: 1308402
Signed-off-by: Gaurav Kumar Garg <ggarg@redhat.com>
Reviewed-on: http://review.gluster.org/13442
Smoke: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
CentOS-regression: Gluster Build System <jenkins@build.gluster.com>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
Diffstat (limited to 'tests')
| -rw-r--r-- | tests/bugs/glusterd/bug-1177132-quorum-validation.t | 18 |
1 files changed, 18 insertions, 0 deletions
diff --git a/tests/bugs/glusterd/bug-1177132-quorum-validation.t b/tests/bugs/glusterd/bug-1177132-quorum-validation.t index 57aec5ccf57..f18b5a178d3 100644 --- a/tests/bugs/glusterd/bug-1177132-quorum-validation.t +++ b/tests/bugs/glusterd/bug-1177132-quorum-validation.t @@ -58,6 +58,24 @@ TEST $CLI_1 volume remove-brick $V0 $H2:$B2/${V0}2 start TEST $CLI_1 volume set $V0 barrier enable TEST $CLI_1 volume remove-brick $V0 $H2:$B2/${V0}2 stop +## Stop the volume +TEST $CLI_1 volume stop $V0 + +## Bring down 2nd glusterd +TEST kill_glusterd 2 + +## Now quorum is not meet. Starting volume on 1st node should not success +TEST ! $CLI_1 volume start $V0 + +## Bring back 2nd glusterd +TEST $glusterd_2 + +# After 2nd glusterd come back, there will be 2 nodes in a clusater +EXPECT_WITHIN $PROBE_TIMEOUT 1 peer_count; + +## Now quorum is meet. Starting volume on 1st node should be success. +TEST $CLI_1 volume start $V0 + # Now re-execute the same profile command and this time it should succeed TEST $CLI_1 volume profile $V0 start |