Bug 1490475

Summary: fence_ilo_ssh configuration is incorrect for resetting host.
Product: Red Hat Enterprise Linux 7 Reporter: Ulhas Surse <usurse>
Component: fence-agentsAssignee: Oyvind Albrigtsen <oalbrigt>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.3CC: cfeist, cluster-maint, dfediuck, mjuricek, sbradley
Target Milestone: pre-dev-freeze   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: fence-agents-4.0.11-77.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 12:16:03 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ulhas Surse 2017-09-11 17:04:58 UTC
Description of problem:
In the fence agent fence_ilo_ssh (/usr/sbin/fence_ilo_ssh) a wrong ILO CLI command is used for doing a reboot cycle.

   conn.send_eol("reset hard /system1")

The command should be:

   conn.send_eol("reset /system1 hard")

Version-Release number of selected component (if applicable):
RHV-H Image NG host
RHEVH from 3.6 also has the same code. 

How reproducible:
Always

Steps to Reproduce:
1. Install RHVH
2. Check for HP iLO reset command
3. Result fails 

Actual results:

 Result:

     status=2
     status_tag=COMMAND PROCESSING FAILED
     error_tag=COMMAND ERROR-UNSPECIFIED

Expected results:

     status=0
     status_tag=COMMAND COMPLETED

Additional info:

1] 
fence-agents-ilo-ssh-4.0.11-47.el7_3.3.x86_64 : Fence agent for HP iLO devices via SSH
fence-agents-ilo-ssh-4.0.11-66.el7.x86_64

2] 
Filename    : /usr/sbin/fence_ilo_ssh

3] 
https://github.com/ClusterLabs/fence-agents/blob/RHEL7/fence/agents/ilo_ssh/fence_ilo_ssh.py

Comment 3 Oyvind Albrigtsen 2017-09-12 14:20:16 UTC
https://github.com/ClusterLabs/fence-agents/pull/141

Comment 11 errata-xmlrpc 2018-04-10 12:16:03 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://access.redhat.com/errata/RHBA-2018:0758