[Bugs] [Bug 1706893] New: Volume stop when quorum not met is successful
bugzilla at redhat.com
bugzilla at redhat.com
Mon May 6 13:02:09 UTC 2019
https://bugzilla.redhat.com/show_bug.cgi?id=1706893
Bug ID: 1706893
Summary: Volume stop when quorum not met is successful
Product: Red Hat Gluster Storage
Version: rhgs-3.5
Hardware: x86_64
OS: Linux
Status: NEW
Component: glusterd
Keywords: Triaged
Severity: medium
Assignee: amukherj at redhat.com
Reporter: kiyer at redhat.com
QA Contact: bmekala at redhat.com
CC: amukherj at redhat.com, bugs at gluster.org,
rhs-bugs at redhat.com, risjain at redhat.com,
sankarshan at redhat.com, srakonde at redhat.com,
storage-qa-internal at redhat.com, vbellur at redhat.com
Depends On: 1690753
Target Milestone: ---
Classification: Red Hat
+++ This bug was initially created as a clone of Bug #1690753 +++
Description of problem:
On a 2 node cluster(N1 &N2), create one volume of type distributed. Now set
cluster.server-quorum-ratio to 90% and set cluster.server-quorum-type to
server. Start the volume and stop glusterd on one of the node. Now if you try
to stop the volume the volumes stops successfully but ideally it shouldn't
stop.
How reproducible:
5/5
Steps to Reproduce:
1. Create a cluster with 2 nodes.
2. Create a volume of type distributed.
3. Set cluster.server-quorum-ratio to 90.
4. Set server-quorum-type to server.
5. Start the volume.
6. Stop glusterd on one node.
7. Stop the volume.(Should fail!)
Actual results:
volume stop: testvol_distributed: success
Expected results:
volume stop: testvol_distributed: failed: Quorum not met. Volume operation not
allowed.
Additional info:
--- Additional comment from Atin Mukherjee on 2019-04-01 14:33:42 UTC ---
This looks like a bug and should be an easy fix.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1690753
[Bug 1690753] Volume stop when quorum not met is successful
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Bugs
mailing list