[Bugs] [Bug 1394883] Failed to enable nfs-ganesha after disabling nfs-ganesha cluster

[bugzilla at redhat.com]

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



--- Comment #4 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/15845 committed in release-3.8 by Kaleb
KEITHLEY (kkeithle at redhat.com) 
------
commit b29c3ec63fa6520bcf169581d0dac6602fed2993
Author: Kaleb S. KEITHLEY <kkeithle at redhat.com>
Date:   Mon Nov 14 11:24:33 2016 -0500

    common-ha: remove /etc/corosync/corosync.conf in teardown/cleanup

    In newer versions of corosync we observe that after tearing down an
    existing HA cluster, when trying to set up a new cluster, `pcs cluster
    start --all` will fail if corosync believes the nodes are already in
    the cluster based on the presence of, and the contents of
    /etc/corosync/corosync.conf

    So we summarily delete it. (An alternative/work-around is to use `pcs
    cluster start --force --all`)

    Change-Id: I225f4e35e3b605e860ec4f9537c40ed94ac68625
    BUG: 1394883
    Signed-off-by: Kaleb S. KEITHLEY <kkeithle at redhat.com>
    Reviewed-on: http://review.gluster.org/15845
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: soumya k <skoduri at redhat.com>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>

-- 
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=j1t2YNfEI3&a=cc_unsubscribe