diff options
| author | Kaleb S. KEITHLEY <kkeithle@redhat.com> | 2016-11-14 11:24:33 -0500 |
|---|---|---|
| committer | Kaleb KEITHLEY <kkeithle@redhat.com> | 2016-11-15 11:45:26 -0800 |
| commit | b29c3ec63fa6520bcf169581d0dac6602fed2993 (patch) | |
| tree | 3f8ca870bcc52fb1c5d5ec924b07bd7f55ebf5f3 /run-tests-in-vagrant.sh | |
| parent | 0f97f880b0d01baf94e10950e63e4bb823ed2e40 (diff) | |
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@redhat.com>
Reviewed-on: http://review.gluster.org/15845
Smoke: Gluster Build System <jenkins@build.gluster.org>
Reviewed-by: soumya k <skoduri@redhat.com>
CentOS-regression: Gluster Build System <jenkins@build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>
Diffstat (limited to 'run-tests-in-vagrant.sh')
0 files changed, 0 insertions, 0 deletions