Bug 1279351 - [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
Blocks: 1282322
  Show dependency treegraph
Reported: 2015-11-09 04:17 EST by Mohammed Rafi KC
Modified: 2016-04-19 03:47 EDT (History)
8 users (show)

See Also:
Fixed In Version: glusterfs-3.7.7
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1279319
: 1282322 (view as bug list)
Last Closed: 2016-04-19 03:47:50 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 06:24:25 EST
REVIEW: http://review.gluster.org/12585 (glusterd: brick failed to start) posted (#1) for review on release-3.7 by mohammed rafi  kc (rkavunga@redhat.com)
Comment 2 Vijay Bellur 2015-11-16 09:18:03 EST
COMMIT: http://review.gluster.org/12585 committed in release-3.7 by Dan Lambright (dlambrig@redhat.com) 
commit cc7367bcde55c315a299aa97d521d25424f15e76
Author: Mohammed Rafi KC <rkavunga@redhat.com>
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
    back port of >
    >Change-Id: I3b16ee29de19c5d34e45d77d6b7e4b665c2a4653
    >BUG: 1282322
    >Signed-off-by: Mohammed Rafi KC <rkavunga@redhat.com>
    >Reviewed-on: http://review.gluster.org/12552
    >Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    >Tested-by: Gluster Build System <jenkins@build.gluster.com>
    >Reviewed-by: Atin Mukherjee <amukherj@redhat.com>
    (cherry picked from commit 571cbcf56ef865d64ebdb1621c791fe467501e52)
    Change-Id: I3b16ee29de19c5d34e45d77d6b7e4b665c2a4653
    BUG: 1279351
    Reviewed-on: http://review.gluster.org/12585
    Tested-by: NetBSD Build System <jenkins@build.gluster.org>
    Tested-by: Gluster Build System <jenkins@build.gluster.com>
    Reviewed-by: Dan Lambright <dlambrig@redhat.com>
    Tested-by: Dan Lambright <dlambrig@redhat.com>
Comment 3 Kaushal 2016-04-19 03:47:50 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.7.7, please open a new bug report.

glusterfs-3.7.7 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.

[1] https://www.gluster.org/pipermail/gluster-users/2016-February/025292.html
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user

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