[Bugs] [Bug 1367478] Second gluster volume is offline after daemon restart or server reboot

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1367478



--- Comment #2 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/15183 committed in master by Atin Mukherjee
(amukherj at redhat.com) 
------
commit dd8d93f24a320805f1f67760b2d3266555acf674
Author: Samikshan Bairagya <samikshan at gmail.com>
Date:   Tue Aug 16 16:46:41 2016 +0530

    glusterd: Fix volume restart issue upon glusterd restart

    http://review.gluster.org/#/c/14758/ introduces a check in
    glusterd_restart_bricks that makes sure that if server quorum is
    enabled and if the glusterd instance has been restarted, the bricks
    do not get started. This prevents bricks which have been brought
    down purposely, say for maintainence, from getting started
    upon a glusterd restart. However this change introduced regression
    for a situation that involves multiple volumes. The bricks from
    the first volume get started, but then for the subsequent volumes
    the bricks do not get started. This patch fixes that by setting
    the value of conf->restart_done to _gf_true only after bricks are
    started correctly for all volumes.

    Change-Id: I2c685b43207df2a583ca890ec54dcccf109d22c3
    BUG: 1367478
    Signed-off-by: Samikshan Bairagya <samikshan at gmail.com>
    Reviewed-on: http://review.gluster.org/15183
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Atin Mukherjee <amukherj at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=oEFqPtVGHb&a=cc_unsubscribe