In my 2 node test cluster, one node is a physical server (running
Pacemaker 1.1.13), the other is a VM on that server, configured as a
Pacemaker remote node (v1.1.13).
I get the correct output if I run crm_mon & pcs config on the remote
node, but if I run 'pcs status' I get
# pcs statu
On 12/02/2015 06:21 AM, Simon Lawrence wrote:
>
> In my 2 node test cluster, one node is a physical server (running
> Pacemaker 1.1.13), the other is a VM on that server, configured as a
> Pacemaker remote node (v1.1.13).
>
> I get the correct output if I run crm_mon & pcs config on the remote
>
On 02/12/15 16:37, Ken Gaillot wrote:
On 12/02/2015 06:21 AM, Simon Lawrence wrote:
In my 2 node test cluster, one node is a physical server (running
Pacemaker 1.1.13), the other is a VM on that server, configured as a
Pacemaker remote node (v1.1.13).
I get the correct output if I run crm_mon &
Hi, Kristoffer
I think Markus's points out and patch is correct.
And I want some advice for that what gethosts should return.
>> The bug is not really a bug in the fencing agent, but in the Python
>> AWS API CLI. It looks like, that sometimes, when calling two or more
>> 'aws ec2 ...' commands in
Hi, Kristoffer
>> The 'gethostlist' code seems to be a bit strange:
>Indeed, it should return only the hostnames in the "tag"
>And, if the "port" is set, it should return only value of "port".
>(Is the first if-clause not necessary?)
>
>This plug-in is based on the following.
> https://github
