Bug 1298594 - RHEV-M hypervisor fencing fails with error "Failed to run Power Management command on Host , no running proxy Host was found"
Summary: RHEV-M hypervisor fencing fails with error "Failed to run Power Management co...
Keywords:
Status: CLOSED DUPLICATE of bug 1260619
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.5.3
Hardware: All
OS: Linux
high
urgent
Target Milestone: ---
: ---
Assignee: Eli Mesika
QA Contact:
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-14 13:58 UTC by nijin ashok
Modified: 2019-10-10 10:54 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-22 14:17:30 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.