18.07.2018 04:21, Confidential Company пишет:
>>> Hi,
>>>
>>> On my two-node active/passive setup, I configured fencing via
>>> fence_vmware_soap. I configured pcmk_delay=0 on both nodes so I
>> expected
>>> that both nodes will be stonithed simultaenously.
>>>
>>> On my test scenario, Node1 has
> > Hi,
> >
> > On my two-node active/passive setup, I configured fencing via
> > fence_vmware_soap. I configured pcmk_delay=0 on both nodes so I
> expected
> > that both nodes will be stonithed simultaenously.
> >
> > On my test scenario, Node1 has ClusterIP resource. When I
> disconnect
> >
Upon further investigation, there is no problem when resource agents
are called by the cluster, which thankfully makes this issue less
significant.
The problem occurs when "crm_node -n" is called on the command line or
by a script, on a Pacemaker Remote node running 1.1.19 or 2.0.0 or
later, with
On 16/07/18 11:44 +0200, Philipp Achmüller wrote:
> Unfortunatly it is not obvious for me - the "grep fence" is attached
> in my original message.
Sifting your logs a bit:
> ---
> Node: siteb-2 (DC):
> 2018-06-28T09:02:23.282153+02:00 siteb-2 pengine[189259]: notice: Move
>
On Tue, 2018-07-17 at 21:29 +0800, Confidential Company wrote:
>
> > Hi,
> >
> > On my two-node active/passive setup, I configured fencing via
> > fence_vmware_soap. I configured pcmk_delay=0 on both nodes so I
> expected
> > that both nodes will be stonithed simultaenously.
> >
> > On my test
I am happy to announce the first alpha of pcs-0.10: pcs-0.10.0.alpha.1.
Source code is available at:
https://github.com/ClusterLabs/pcs/archive/0.10.0.alpha.1.tar.gz
or
https://github.com/ClusterLabs/pcs/archive/0.10.0.alpha.1.zip
Pcs-0.10 is the new main pcs branch supporting Corosync 3.x and
> Hi,
>
> On my two-node active/passive setup, I configured fencing via
> fence_vmware_soap. I configured pcmk_delay=0 on both nodes so I expected
> that both nodes will be stonithed simultaenously.
>
> On my test scenario, Node1 has ClusterIP resource. When I disconnect
> service/corosync link
On Tue, Jul 17, 2018 at 10:58 AM, Confidential Company
wrote:
> Hi,
>
> On my two-node active/passive setup, I configured fencing via
> fence_vmware_soap. I configured pcmk_delay=0 on both nodes so I expected
> that both nodes will be stonithed simultaenously.
>
> On my test scenario, Node1 has
Hi,
On my two-node active/passive setup, I configured fencing via
fence_vmware_soap. I configured pcmk_delay=0 on both nodes so I expected
that both nodes will be stonithed simultaenously.
On my test scenario, Node1 has ClusterIP resource. When I disconnect
service/corosync link physically,
