>>> Valentin Vidic schrieb am 03.03.2020 um
16:52
in Nachricht
<20449_1583250783_5e5e7d5f_20449_2155_1_20200303155240.ga24...@valentin-vidic.fr
m.hr>:
> On Sat, Feb 29, 2020 at 03:44:50PM ‑0600, Ken Gaillot wrote:
>> The clusterlabs.org server OS upgrade is (mostly) done.
>>
>> Services are
>>> schrieb am 03.03.2020 um 15:22 in Nachricht
<21288_1583245382_5e5e6846_21288_1264_1_87zhcx1psd@lant.ki.iif.hu>:
> Hi,
>
> I suffered unexpected fencing under Pacemaker 2.0.1. I set a resource
> to unmanaged (crm_resource ‑r vm‑invtest ‑m ‑p is‑managed ‑v false),
> then played with
On 3/3/20 11:22 PM, wf...@niif.hu wrote:
Hi,
I suffered unexpected fencing under Pacemaker 2.0.1. I set a resource
to unmanaged (crm_resource -r vm-invtest -m -p is-managed -v false),
then played with ocf-tester, which left the resource stopped. Finally I
deleted the resource (crm_resource -r
Quoting Jaap Winius :
Very interesting. I'm already running DRBD 9, so that base has
already been covered, but here's some extra information: My test
system actually consists of a single 4-node DRBD cluster that spans
two data centers, with each data center having a 2-node Pacemaker
On Sat, Feb 29, 2020 at 03:44:50PM -0600, Ken Gaillot wrote:
> The clusterlabs.org server OS upgrade is (mostly) done.
>
> Services are back up, with the exception of some cosmetic issues and
> the source code continuous integration testing for ClusterLabs github
> projects (ci.kronosnet.org).
Hi,
I suffered unexpected fencing under Pacemaker 2.0.1. I set a resource
to unmanaged (crm_resource -r vm-invtest -m -p is-managed -v false),
then played with ocf-tester, which left the resource stopped. Finally I
deleted the resource (crm_resource -r vm-invtest --delete -t primitive),
which
