Description of problem: ===================== the ideal way of configuring ec volumes is to have all bricks in different nodes(no 2 bricks of same dht-subvol must be on same node) that is why when we create an ec volume and we use same hostname for 2 bricks of same dht-subvol, it fails saying it is not optimal user must use force to over-ride this behavior, which is perfect. However the same check is not made when we do an add-brick Version-Release number of selected component (if applicable): ================== 3.12.2-1 How reproducible: ==== always Steps to Reproduce: 1.create a 4+2 ec vol on 6 node setup 2. now add a new subvol of 6 bricks such that 2 bricks are hosted by n1 , 2 by n2 and 2 by n3 Actual results: add brick passes without any warns/errors Expected results: ========= must fail and throw a error saying this is not optimal setup and user must use force
REVIEW: https://review.gluster.org/23729 (glusterd: check for same node while adding bricks in disperse volume) posted (#4) for review on master by Sheetal Pamecha
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