--power-timeout from default (20
seconds), also you can add -v to have verbose output.
As long as you have same version of fence-agents-common and
fence-agents-vmware, there should be no issues.
m,
On Fri, Jul 1, 2016 at 11:31 AM, Kevin THIERRY
<kevin.thierry.cit...@gmail.com
<ma
2.6.0
CPython/2.7.5 Linux/3.10.0-327.18.2.el7.x86_64)
I am wondering if there is some kind of compatibility issue. I am using
fence-agents-vmware-soap 4.0.11 on CentOS 7.2.1511 and ESXi 6.0.0 Build
2494585.
Any ideas about that issue?
Best regards,
--
Kevin THIERRY
IT System Engineer
CI
06/15/2016 02:18 PM, Kevin THIERRY wrote:
Hello !
I wasn't expecting such great explanations, thanks a lot Ken ! Also
thank you for your example Dimitri ! It solved the issue I had !
I'm still having trouble though: when I make the primary node fail (I
unplug it), the secondary node star
PING
pcs cluster cib ping_cfg
pcs -f ping_cfg resource create ping ocf:pacemaker:ping dampen=5s
multiplier=1000 host_list="10.5.200.254" --clone
pcs -f ping_cfg constraint location vip rule score=-INFINITY pingd lt 1
or not_defined pingd
pcs cluster cib-push ping_cfg
--
Kevin THIERRY
IT