Hey Marek, I've run the command with --action off and uploaded the file on one of our servers : https://cloud.iwgate.com/index.php/s/1SpZlG8mBSR1dNE
Interesting thing is that at the end of the file I found "Unable to connect/login to fencing device" instead of "Failed: Timed out waiting to power OFF" As information about my test rig: Host OS: VMware ESXi 6.5 Hypervisor Guest OS: Centos 7.3.1611 minimal with the latest updates Fence agents installed with yum : fence-agents-hpblade-4.0.11-47.el7_3.5.x86_64 fence-agents-rsa-4.0.11-47.el7_3.5.x86_64 fence-agents-ilo-moonshot-4.0.11-47.el7_3.5.x86_64 fence-agents-rhevm-4.0.11-47.el7_3.5.x86_64 fence-virt-0.3.2-5.el7.x86_64 fence-agents-mpath-4.0.11-47.el7_3.5.x86_64 fence-agents-ibmblade-4.0.11-47.el7_3.5.x86_64 fence-agents-ipdu-4.0.11-47.el7_3.5.x86_64 fence-agents-common-4.0.11-47.el7_3.5.x86_64 fence-agents-rsb-4.0.11-47.el7_3.5.x86_64 fence-agents-ilo-ssh-4.0.11-47.el7_3.5.x86_64 fence-agents-bladecenter-4.0.11-47.el7_3.5.x86_64 fence-agents-drac5-4.0.11-47.el7_3.5.x86_64 fence-agents-brocade-4.0.11-47.el7_3.5.x86_64 fence-agents-wti-4.0.11-47.el7_3.5.x86_64 fence-agents-compute-4.0.11-47.el7_3.5.x86_64 fence-agents-eps-4.0.11-47.el7_3.5.x86_64 fence-agents-cisco-ucs-4.0.11-47.el7_3.5.x86_64 fence-agents-intelmodular-4.0.11-47.el7_3.5.x86_64 fence-agents-eaton-snmp-4.0.11-47.el7_3.5.x86_64 fence-agents-cisco-mds-4.0.11-47.el7_3.5.x86_64 fence-agents-apc-snmp-4.0.11-47.el7_3.5.x86_64 fence-agents-ilo2-4.0.11-47.el7_3.5.x86_64 fence-agents-all-4.0.11-47.el7_3.5.x86_64 fence-agents-vmware-soap-4.0.11-47.el7_3.5.x86_64 fence-agents-ilo-mp-4.0.11-47.el7_3.5.x86_64 fence-agents-apc-4.0.11-47.el7_3.5.x86_64 fence-agents-emerson-4.0.11-47.el7_3.5.x86_64 fence-agents-ipmilan-4.0.11-47.el7_3.5.x86_64 fence-agents-ifmib-4.0.11-47.el7_3.5.x86_64 fence-agents-kdump-4.0.11-47.el7_3.5.x86_64 fence-agents-scsi-4.0.11-47.el7_3.5.x86_64 Thank you On Tue, Aug 1, 2017 at 2:22 PM, Marek Grac <mg...@redhat.com> wrote: > Hi, > > > But when I call any of the power actions (on, off, reboot) I get "Failed: >> > Timed out waiting to power OFF". >> > >> > I've tried with all the combinations of --power-timeout and --power-wait >> > and same error without any change in the response time. >> > >> > Any ideas from where or how to fix this issue ? >> > > No, you have used the right options and if they were high enough it should > work. You can try to post verbose (anonymized) output and we can take a > look at it more deeply. > > >> >> I suspect "power off" is actually a virtual press of the ACPI power >> button (reboot likewise), so your VM tries to shut down cleanly. That could >> take time, and it could hang (I guess). I don't use VMware, but maybe >> there's a "reset" action that presses the virtual reset button of the >> virtual hardware... ;-) >> > > There should not be a fence agent that will do soft reboot. The 'reset' > action does power off/check status/power on so we are sure that machine > was really down (of course unless --method cycle when 'reboot' button is > used). > > m, > > _______________________________________________ > Users mailing list: Users@clusterlabs.org > http://lists.clusterlabs.org/mailman/listinfo/users > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > >
_______________________________________________ Users mailing list: Users@clusterlabs.org http://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org