Bugzilla will be upgraded to version 5.0 on December 2, 2018. The outage period for the upgrade will start at 0:00 UTC and have a duration of 12 hours

Bug 864772

Summary: Add-brick fails to start bricks when more than one is supplied in CLI
Product: [Community] GlusterFS Reporter: krishnan parthasarathi <kparthas>
Component: glusterdAssignee: krishnan parthasarathi <kparthas>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: gluster-bugs, nsathyan
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: glusterfs-3.4.0 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-24 13:33:20 EDT Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description krishnan parthasarathi 2012-10-10 01:06:00 EDT
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

How reproducible:

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.
Actual results:
Only the last brick in the list of bricks supplied is started

Expected results:
All the bricks supplied to add-brick must be started.

Additional info:
Offending commit - http://review.gluster.com/3668
Comment 1 Vijay Bellur 2012-10-10 22:20:18 EDT
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 (avati@redhat.com)