Project

General

Profile

Actions

Fix #5011

closed

plana65 reboot or ipmi fail

Added by Sage Weil almost 11 years ago. Updated almost 11 years ago.

Status:
Resolved
Priority:
High
Assignee:
Sandon Van Ness
Category:
-
Target version:
% Done:

100%

Source:
other
Tags:
Backport:
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):

Description

ubuntu@teuthology:/var/lib/teuthworker/archive/teuthology-2013-05-10_01:00:06-rados-master-testing-basic/10278$ tail teuthology.log
2013-05-10T10:43:34.875 DEBUG:teuthology.orchestra.remote:expect: plana65 login
2013-05-10T10:48:34.424 DEBUG:teuthology.orchestra.remote:expect before: [SOL Session operational. Use ~? for help]

2013-05-10T10:48:34.424 DEBUG:teuthology.orchestra.remote:expect after: <class 'pexpect.TIMEOUT'>
2013-05-10T10:48:34.476 DEBUG:teuthology.orchestra.remote:pexpect command: ipmitool -H plana65.ipmi.sepia.ceph.com -I lanplus -U inktank -P ApGNXcA7 sol activate
2013-05-10T10:48:34.628 DEBUG:teuthology.orchestra.remote:expect: plana65 login
2013-05-10T10:53:34.478 DEBUG:teuthology.orchestra.remote:expect before: [SOL Session operational. Use ~? for help]

2013-05-10T10:53:34.478 DEBUG:teuthology.orchestra.remote:expect after: <class 'pexpect.TIMEOUT'>
2013-05-10T10:53:34.530 INFO:teuthology.orchestra.remote:Failed to get ipmi console status for plana65: Timeout exceeded (300) for 6 attempts in _wait_for_login()

Actions #1

Updated by Sandon Van Ness almost 11 years ago

  • Assignee set to Sandon Van Ness
Actions #2

Updated by Anonymous almost 11 years ago

  • Tracker changed from Bug to Fix
Actions #3

Updated by Anonymous almost 11 years ago

  • Target version set to v0.65
Actions #4

Updated by Anonymous almost 11 years ago

  • Translation missing: en.field_story_points set to 1.00
Actions #5

Updated by Sandon Van Ness almost 11 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

The powercycle went through ok but never came back up for some reason (nothing on SOL). Manually doing a power cycle brought it back up. I will mark it as a machine that has had problems to see if it happens again in the future.

Actions

Also available in: Atom PDF