Description of problem: =========================== currently we only support volumes of replica count 3 Any volume with replica count 2 throws a warning (which again needs a bit of modification as mentioned in BZ#1763124) however glusterfs still create a volume of replica count >3 as below example, without any caution/warning. [root@dhcp35-190 ~]# gluster v create rep rep 4 dhcp35-237.lab.eng.blr.redhat.com:/gluster/brick1/rep2 $HOSTNAME:/gluster/brick1/rep2 dhcp35-29.lab.eng.blr.redhat.com:/gluster/brick1/rep2 dhcp35-157.lab.eng.blr.redhat.com:/gluster/brick1/rep2 volume create: rep: success: please start the volume to access data We must throw a warning saying that " replica count other than or greater than 3 is not supported," Version-Release number of selected component (if applicable): 6.0.18
upstream patch: https://review.gluster.org/#/c/glusterfs/+/23566
This should be a fairly simple tests to automate. Do we have it automated?
(In reply to Yaniv Kaul from comment #7) > This should be a fairly simple tests to automate. Do we have it automated? Not yet automated
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (glusterfs bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:5603