Red Hat Bugzilla – Bug 864772
Add-brick fails to start bricks when more than one is supplied in CLI
Last modified: 2015-11-03 18:04:50 EST
Description of problem:
# gluster volume add-brick <volname> host1:brick1 host2:brick2
Add-brick returns success. But on running volume-status (on a started volume), we find that only the last brick in the list of bricks supplied is started.
Version-Release number of selected component (if applicable):
144db7f39f35a51c24558c81faea3f49c237312f on master
Steps to Reproduce:
1. Create a glusterfs volume.
2. Start the volume.
3. Add more than one brick in a single add-brick command
4. Run volume-status to check if all bricks are running.
Only the last brick in the list of bricks supplied is started
All the bricks supplied to add-brick must be started.
Offending commit - http://review.gluster.com/3668
CHANGE: http://review.gluster.org/4051 (glusterd: add-brick failed to start bricks when more than one were given) merged in master by Anand Avati (email@example.com)