Description of problem: ------------------------ When trying to reduce the replica count of a distribute-replicate volume by removing one brick each from all the replica groups, the command fails with different error messages if the brick being removed are specified in different order. For example - [root@localhost ~]# gluster volume info disrep-vol Volume Name: disrep-vol Type: Distributed-Replicate Volume ID: 33334784-2f07-4d34-a768-046b72011ed2 Status: Created Number of Bricks: 2 x 3 = 6 Transport-type: tcp Bricks: Brick1: 10.70.37.109:/tmp/br1 Brick2: 10.70.37.120:/tmp/br2 Brick3: 10.70.37.177:/tmp/br3 Brick4: 10.70.37.182:/tmp/br4 Brick5: 10.70.37.109:/tmp/br5 Brick6: 10.70.37.120:/tmp/br6 Consider the following commands - [root@localhost ~]# gluster volume remove-brick disrep-vol replica 2 10.70.37.109:/tmp/br1 10.70.37.182:/tmp/br4 force Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y volume remove-brick commit force: failed: Reducing replica count of volume is disallowed in glusterfs 3.4.0.47.1u2rhs [root@localhost ~]# gluster volume remove-brick disrep-vol replica 2 10.70.37.182:/tmp/br4 10.70.37.109:/tmp/br1 force Removing brick(s) can result in data loss. Do you want to Continue? (y/n) y volume remove-brick commit force: failed: Bricks are from same subvol The command should always fail with the correct error message. Version-Release number of selected component (if applicable): glusterfs 3.4.0.47.1u2rhs How reproducible: Always Steps to Reproduce: 1. From a 2x3 distribute-replicate volume, remove one brick from each replica set, by listing the bricks in the same order as volume info list them. It fails with the message that the operation is disallowed. 2. Now remove the same bricks but with the bricks interchanged in order. Actual results: It fails with the wrong error message. Expected results: The command should fail with the correct error message always. Additional info:
Per bug triage 12/11, removing from corbett list
Downstream patch : https://code.engineering.redhat.com/gerrit/#/c/17469/
It's required by RHSC, but not a huge blocker. Considering it's already fixed, it will be good to be in Corbett.
Priority: unspecified; severity: medium; does not fall in MUST FIX bucket for Corbett (including both RHS and RHSC) and hence qa_ack- Feel free to raise the blocker flag with enough comment in case I have missed anything here and we can triage again.
Quality Engineering Management has reviewed and declined this request. You may appeal this decision by reopening this request.
Reverting to state of the bug, "Status: MODIFIED"
Please set priority.
Verified as fixed in glusterfs 3.4.0.50rhs. Tried removing bricks ordered in different ways, the operation failed with the same error message - volume remove-brick commit force: failed: Reducing replica count of volume is disallowed in glusterfs 3.4.0.50rhs
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, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2014-0208.html