diff options
| author | Kaleb S. KEITHLEY <kkeithle@redhat.com> | 2016-11-14 11:09:31 -0500 |
|---|---|---|
| committer | Kaleb KEITHLEY <kkeithle@redhat.com> | 2016-11-15 11:30:26 -0800 |
| commit | 8437b24de36d322d26f707890f25392a098de30e (patch) | |
| tree | 27d8f9e6b7feb8d287ad3e98f722ce71ca856573 /extras/backend-cleanup.sh | |
| parent | a35d63050ec7e745a66c1aef8e1c8eb42d7b67a1 (diff) | |
| download | glusterfs-8437b24de36d322d26f707890f25392a098de30e.tar.gz glusterfs-8437b24de36d322d26f707890f25392a098de30e.tar.xz glusterfs-8437b24de36d322d26f707890f25392a098de30e.zip | |
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: 1394881
Signed-off-by: Kaleb S. KEITHLEY <kkeithle@redhat.com>
Reviewed-on: http://review.gluster.org/15843
Smoke: Gluster Build System <jenkins@build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: soumya k <skoduri@redhat.com>
Diffstat (limited to 'extras/backend-cleanup.sh')
0 files changed, 0 insertions, 0 deletions