Red Hat Bugzilla – Bug 1282322
[GlusterD]: Volume start fails post add-brick on a volume which is not started
Last modified: 2016-06-16 09:44:23 EDT
REVIEW: http://review.gluster.org/12552 (glusterd: brick failed to start) posted (#3) for review on master by mohammed rafi kc (firstname.lastname@example.org)
COMMIT: http://review.gluster.org/12552 committed in master by Atin Mukherjee (email@example.com)
Author: Mohammed Rafi KC <firstname.lastname@example.org>
Date: Mon Nov 9 16:43:21 2015 +0530
glusterd: brick failed to start
brick volfiles are generated in post validate, if
it is running version higher than GLUSTER_3_7_5,
else will be running in syncop.
If the code fall back to syncop, and volume is stopped
then we were returning the operation with out generating
Signed-off-by: Mohammed Rafi KC <email@example.com>
Tested-by: NetBSD Build System <firstname.lastname@example.org>
Tested-by: Gluster Build System <email@example.com>
Reviewed-by: Atin Mukherjee <firstname.lastname@example.org>
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see email@example.com with any questions
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.
glusterfs-3.8.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.