Bug 1140098

Summary: [RHEV-M] System is not power on after a fencing operation in power management (agent: ipmilan)
Product: Red Hat Enterprise Virtualization Manager Reporter: Ulhas Surse <usurse>
Component: ovirt-engineAssignee: Eli Mesika <emesika>
Status: CLOSED ERRATA QA Contact: sefi litmanovich <slitmano>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.4.0CC: ecohen, emesika, iheim, lpeer, oourfali, pstehlik, rbalakri, Rhev-m-bugs, sherold, usurse, yeylon
Target Milestone: ---   
Target Release: 3.5.0   
Hardware: All   
OS: Linux   
Whiteboard: infra
Fixed In Version: org.ovirt.engine-root-3.5.0-15 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-11 18:08:59 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:
Bug Depends On:    
Bug Blocks: 1156162    

Description Ulhas Surse 2014-09-10 09:56:58 UTC
Description of problem:
Host is not power on when "restart" option in power management is selected from RHEVM GUI. Host is powered off istead of reboot.

Version-Release number of selected component (if applicable):
RHEVM 3.4 
rhevm-3.4.1-0.31.el6ev.noarch
vdsm-4.14.11-5.el6ev.x86_64

How reproducible:
always

Steps to Reproduce:
1. Install two hosts.
2. configure power management on these hosts.
3. try to restart from RHEVM gui under "power management" option.


Actual results:
Host is shut off

Expected results:
Host should reboot and come up again.

Additional info:
Hardware Information:

Hardware - 3x Dell PowerEdge R720 with iDRAC 7 
             iDRAC firmware version 1.57.57

[matching bug in 3.3 - https://bugzilla.redhat.com/show_bug.cgi?id=1093742] I have not checked above issue with 3.3

Comment 1 Eli Mesika 2014-09-10 12:39:27 UTC
please attach engine and vdsm logs

Comment 26 sefi litmanovich 2014-10-23 09:38:33 UTC
Verified with rhevm-3.5.0-0.17.beta.el6ev.noarch, hosts with vdsm-4.16.7.1-1.el6ev.x86_64, fence-agents-3.1.5-48.el6.x86_64.

1. 2 hosts in same cluster, one with PM configured.
2. connected to psql and updated the waiting time between stopstatus retries:

"update vdc_options set option_value = '30' where option_name = 'FenceStopStatusRetries';"

3. restart engine.
4. issue fence restart on the host with pm.

5. wait for stop command to be issued and immediately block connection between proxy host and host_with_pm's fence agent (using iptables).

6. verify that first status command returns 'unknown'.
7. undo block in (5) (iptables restart).
8. verify that second status is issued and returns 'off'.

Comment 28 errata-xmlrpc 2015-02-11 18:08:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0158.html