[Bugs] [Bug 1330097] ganesha exported volumes doesn't get synced up on shutdown node when it comes up.

bugzilla at redhat.com bugzilla at redhat.com
Fri May 6 06:12:43 UTC 2016


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



--- Comment #13 from Vijay Bellur <vbellur at redhat.com> ---
COMMIT: http://review.gluster.org/14063 committed in master by Atin Mukherjee
(amukherj at redhat.com) 
------
commit f71e2fa49af185779b9f43e146effd122d4e9da0
Author: Jiffin Tony Thottan <jthottan at redhat.com>
Date:   Mon Apr 18 21:34:32 2016 +0530

    glusterd-ganesha : copy ganesha export configuration files during reboot

    glusterd creates export conf file for ganesha using hook script during
    volume start and ganesha_manage_export() for volume set command. But this
    routine is not added in glusterd restart scenario.
    Consider the following case, in a three node cluster a volume got exported
    via ganesha while one of the node is offline(glusterd is not running).
    When the node comes back online, that volume is not exported on that node
    due to the above mentioned issue.
    Also I have removed unused variables from glusterd_handle_ganesha_op()
    For this patch to work pcs cluster should running on that be node.

    Change-Id: I5b2312c2f3cef962b1f795b9f16c8f0a27f08ee5
    BUG: 1330097
    Signed-off-by: Jiffin Tony Thottan <jthottan at redhat.com>
    Reviewed-on: http://review.gluster.org/14063
    Smoke: Gluster Build System <jenkins at build.gluster.com>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: soumya k <skoduri at redhat.com>
    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=K86XmExlRp&a=cc_unsubscribe


More information about the Bugs mailing list