Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 522529

Summary: ipmi fence failed
Product: Red Hat Enterprise Linux 5 Reporter: Benjamin Kahn <bkahn>
Component: cmanAssignee: Jan Friesse <jfriesse>
Status: CLOSED ERRATA QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: urgent    
Version: 5.5CC: ccaulfie, cfeist, cluster-maint, djansa, edamato, ffotorel, phil, pkennedy, pm-eus, rlerch
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: cman-2_0_115-1_el5_4_3 Doc Type: Bug Fix
Doc Text:
Cause: ======= Strange behavior of some HW IPMI implementations (for example IBM x3550, brand new supermicro motherboard). Consequence: ============ Old behavior: perhaps (chassis power status) chassis power off chassis power status (wait for this to return "off") chassis power on chassis power status (wait for this to return "on") and the BMC controller for some difficult to understand reason shuts itself down after the "chassis power off", so it will be not able to power on machine. Fix: ==== Add support for power cycle command, which doesn't shut BMC controller. Result: ======= Old behavior is default, so nothing change without reconfiguration. But now, there is new method option, which can have value cycle, what will cause a new behavior (use ipmi power cycle command). Example of usage:... <fencedevices> <fencedevice agent="fence_ipmilan_new" ipaddr="1.2.3.4" login="root" name="ipmifd1" passwd="password" method="cycle" /> ...
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-10-20 08:20:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 482913, 576036    
Bug Blocks:    
Attachments:
Description Flags
Backport from RHEL 5.5 none

Description Benjamin Kahn 2009-09-10 15:43:17 UTC
This bug has been copied from bug #482913 and has been proposed
to be backported to 5.4 z-stream (EUS).

Comment 3 Jan Friesse 2009-09-29 08:19:48 UTC
Created attachment 362973 [details]
Backport from RHEL 5.5

Attached patch is backport from 5.5 and it's same as patch for RHBZ#482913.

GIT SHA1: fea471dc31137bb3c2583f369cf3af4a0e7eefcb

Comment 4 Jan Friesse 2009-09-29 08:21:55 UTC
Release note added. If any revisions are required, please set the 
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.

New Contents:
Cause:
=======
Strange behavior of some HW IPMI implementations (for example IBM x3550, brand new supermicro motherboard).

Consequence:
============
Old behavior:
perhaps (chassis power status)
chassis power off
chassis power status (wait for this to return "off")
chassis power on
chassis power status (wait for this to return "on")

and the BMC controller for some difficult to understand reason shuts itself
down after the "chassis power off", so it will be not able to power on machine.

Fix:
====
Add support for power cycle command, which doesn't shut BMC controller.

Result:
=======
Old behavior is default, so nothing change without reconfiguration. But now, there is new method option, which can have value cycle, what will cause a new behavior (use ipmi power cycle command).

Example of usage:...

  <fencedevices>
                <fencedevice agent="fence_ipmilan_new" ipaddr="1.2.3.4"
login="root" name="ipmifd1" passwd="password" method="cycle" />
...

Comment 8 errata-xmlrpc 2009-10-20 08:20:03 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-1516.html