Bug 1298594

Summary: RHEV-M hypervisor fencing fails with error "Failed to run Power Management command on Host , no running proxy Host was found"
Product: Red Hat Enterprise Virtualization Manager Reporter: nijin ashok <nashok>
Component: ovirt-engineAssignee: Eli Mesika <emesika>
Status: CLOSED DUPLICATE QA Contact:
Severity: urgent Docs Contact:
Priority: high    
Version: 3.5.3CC: ecohen, emesika, gklein, lsurette, mperina, nashok, oourfali, rbalakri, Rhev-m-bugs, yeylon, ylavi
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: infra
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-22 14:17:30 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Infra RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description nijin ashok 2016-01-14 13:58:05 UTC 
Description of problem:

When one of the host went non responsive , the proxy host try to fence the hypervisor. According to the vdsm logs, fence test operation seems to be success. However after the ovirt engine issues a restart command, the operation fails with error

Failed to run Power Management command on Host , no running proxy Host was found.


Version-Release number of selected component (if applicable):
Red Hat Enterprise Virtualization 3.5

How reproducible:
100% in customer environment

Steps to Reproduce:
1. Configure the power management in the hypervisor.

2. Cut the network connectivity between the hypervisor and RHEV-M

3. The fencing fails with error "Failed to run Power Management command on Host , no running proxy Host was found."

Actual results:

RHEV-M hypervisor fencing fails with error "Failed to run Power Management command on Host , no running proxy Host was found"

Expected results:

Fencing should be success as the proxy host is up and fence "status" check is working.

Additional info:
Comment 5 Eli Mesika 2016-01-19 13:34:41 UTC 
Hi

Please provide the output of the following command from  rhevh1.ongc.ongcgroup.co.in 

vdsClient -s 0 getVdsCaps | grep clusterLevels
Comment 12 Oved Ourfali 2016-01-22 14:17:30 UTC 

*** This bug has been marked as a duplicate of bug 1260619 ***