Hide Forgot
Description of problem: FenceVdsVDSCommand successfully completes even if the underlying fence action to stop, start or reboot a host fails. Version-Release number of selected component (if applicable): rhevm-3.2.3-0.43.el6ev.noarch How reproducible: Always. Steps to Reproduce: 1. Remove all power to an active host, including any fence agents that are configured. 2. Engine will attempt to fence the host in question. 3. The first fence action to stop power will succeed even if the fence command executed by the proxy host fails. Actual results: FenceVdsVDSCommand completes successfully. Expected results: FenceVdsVDSCommand should fail and reflect the failure of the fence command on the proxy. Additional info:
please specify what do exactly do in (taken from BZ description) 1. Remove all power to an active host, including any fence agents that are configured. I need exact steps in UI/API in order to reproduce. NOTE: You wrote : *************** Reading the code we don't actually wait around for the return value when calling the off action thus incorrectly report everything as fine when you can see a return code of 1 above. *************** Yes, the vdsm fenceNode is fire & forget , so success is returned on being able to run the corresponding /usr/sbin/fence_<agent> script , we track the operation success by pooling the Host status via the PM agent
(In reply to Eli Mesika from comment #4) > please specify what do exactly do in (taken from BZ description) > > 1. Remove all power to an active host, including any fence agents that are > configured. > > I need exact steps in UI/API in order to reproduce. > Just pull all power cords from the server. This will remove power from the server but also from the embedded IPMI fencing device (e.g. HP iLO) thus preventing other hosts from reaching the fence device.