Hi again,
After restarting the vCenter, all worked as expected.
Thanks to all.
Have a nice day.
23 de febrero de 2018 7:59, j...@disroot.org escribió:
> Hi all,
>
> Thanks for your responses.
> With your advice I was able to configure it. I still have to test its
> operation. When it is
> pos
Hi all,
Thanks for your responses.
With your advice I was able to configure it. I still have to test its
operation. When it is possible to restart the vCenter, I will post the results.
Have a nice weekend!
22 de febrero de 2018 16:00, "Tomas Jelinek" escribió:
> Try this:
>
> pcs resource me
Hi,
I am trying to configure the failure-timeout for stonith, but I only can do it
for the other resources.
When try to enable it for stonith, I get this error: "Error: resource
option(s): 'failure-timeout', are not recognized for resource type:
'stonith::fence_vmware_soap'".
Thanks.
22 de fe
Thanks for the responses.
So, if I understand, this is the right behaviour and it does not affect to the
stonith mechanism.
If I remember correctly, the fault status persists for hours until I fix it
manually.
Is there any way to modify the expiry time to clean itself?.
22 de febrero de 2018 1
Hi,
I have a 2 node pacemaker cluster configured with the fence agent vmware_soap.
Everything works fine until the vCenter is restarted. After that, stonith fails
and stop.
[root@node1 ~]# pcs status
Cluster name: psqltest
Stack: corosync
Current DC: node2 (version 1.1.16-12.el7_4.7-94ff4df) -
