Description of problem: When we set cluster.quorum-count to no. number of bricks to be up, it should validate max no of bricks value command can accept. How reproducible: 100% Steps to Reproduce: 1.Create 2x3 distribute replicate volume 2.execute gluster volume set <volname> cluster.quorum-type fixed 3.execute gluster volume set <volname> cluster.quorum-count <no. of bricks to be up> Actual results: gluster volume set <volname> cluster.quorum-count accepts any valune between [1 - 2147483647] Expected results: gluster volume set <volname> cluster.quorum-count should validate max no, of brick count to accept
REVIEW: https://review.gluster.org/19104 (mgmt/glusterd: Adding validation for setting quorum-count) posted (#1) for review on master by Karthik U S
COMMIT: https://review.gluster.org/19104 committed in master by \"Karthik U S\" <ksubrahm> with a commit message- mgmt/glusterd: Adding validation for setting quorum-count In a replicated volume it was allowing to set the quorum-count value between the range [1 - 2147483647]. This patch adds validation for allowing only maximum of replica_count number of quorum-count value to be set on a volume. Change-Id: I13952f3c6cf498c9f2b91161503fc0fba9d94898 BUG: 1529515 Signed-off-by: karthik-us <ksubrahm>
REVIEW: https://review.gluster.org/19671 (mgmt/glusterd: Adding validation for setting quorum-count) posted (#1) for review on release-3.13 by Karthik U S
REVISION POSTED: https://review.gluster.org/19671 (mgmt/glusterd: Adding validation for setting quorum-count) posted (#2) for review on release-3.13 by Karthik U S
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-4.0.0, please open a new bug report. glusterfs-4.0.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2018-March/000092.html [2] https://www.gluster.org/pipermail/gluster-users/