This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 1282322 - [GlusterD]: Volume start fails post add-brick on a volume which is not started
[GlusterD]: Volume start fails post add-brick on a volume which is not started
Product: GlusterFS
Classification: Community
Component: glusterd (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Mohammed Rafi KC
: Triaged, ZStream
Depends On: 1279319 1279351
  Show dependency treegraph
Reported: 2015-11-16 00:48 EST by Mohammed Rafi KC
Modified: 2016-06-16 09:44 EDT (History)
7 users (show)

See Also:
Fixed In Version: glusterfs-3.8rc2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1279351
Last Closed: 2016-06-16 09:44:23 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Comment 1 Vijay Bellur 2015-11-16 00:49:06 EST
REVIEW: (glusterd: brick failed to start) posted (#3) for review on master by mohammed rafi  kc (
Comment 2 Vijay Bellur 2015-11-16 04:20:01 EST
COMMIT: committed in master by Atin Mukherjee ( 
commit 571cbcf56ef865d64ebdb1621c791fe467501e52
Author: Mohammed Rafi KC <>
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
    Change-Id: I3b16ee29de19c5d34e45d77d6b7e4b665c2a4653
    BUG: 1282322
    Signed-off-by: Mohammed Rafi KC <>
    Tested-by: NetBSD Build System <>
    Tested-by: Gluster Build System <>
    Reviewed-by: Atin Mukherjee <>
Comment 3 Mike McCune 2016-03-28 18:22:31 EDT
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see with any questions
Comment 4 Niels de Vos 2016-06-16 09:44:23 EDT
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 [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.


Note You need to log in before you can comment on or make changes to this bug.