Bug 1261610 - Issue powering on ibm-x3550m4-06.lab.eng.brq.redhat.com
Issue powering on ibm-x3550m4-06.lab.eng.brq.redhat.com
Status: CLOSED NOTABUG
Product: Beaker
Classification: Community
Component: lab controller (Show other bugs)
develop
Unspecified Unspecified
unspecified Severity unspecified (vote)
: ---
: ---
Assigned To: beaker-dev-list
tools-bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-09 14:56 EDT by Tzu-Mainn Chen
Modified: 2015-09-13 19:57 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-09-13 19:57:20 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Tzu-Mainn Chen 2015-09-09 14:56:11 EDT
Description of problem:

Whenever I try and power on ibm-x3550m4-06.lab.eng.brq.redhat.com, there is an error.  jburke kindly did some initial investigation and discovered the following:

<jburke> tzumainn, I also see this on the IMM
<jburke> ERROR System 9 sept 2015 02:56:35 PM Sensor Planar Fault transitioned to critical from a less severe state 
<jburke> tzumainn, The way Beaker powers some systems on and off is through a ipmi controller built into the system
<jburke> tzumainn, some time that device "goes out to lunch" and needs to be reset
<jburke> tzumainn, But that is not the case here
<jburke> tzumainn, I just logged in to the ipmi 
<jburke> And I saw that critical error 
<jburke> tzumainn, The ipmi device has an option for me to power on the system.
<jburke> tzumainn, When I try it also fails
<jburke> tzumainn, the fault code I see registered is 0x800702020701ffff

Version-Release number of selected component (if applicable):


How reproducible:

Try to power on the machine.

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

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