Bug 682672

Summary: reboot testing abort on RHEL6.1
Product: [Retired] Red Hat Hardware Certification Program Reporter: chen yuwen <yuchen>
Component: Test Suite (tests)Assignee: Greg Nichols <gnichols>
Status: CLOSED ERRATA QA Contact: Guangze Bai <gbai>
Severity: medium Docs Contact:
Priority: medium    
Version: 1.2CC: czhang, gbai, rlandry, ykun, yshao
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-09 16:15:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
hardwaretest.py patch fixing traceback on v7 continue none

Description chen yuwen 2011-03-07 08:33:25 UTC
Description of problem:
Reboot testing run normally. 
But after reboot, error come up at the stage of "v7 continue", and return ABORT.

Error log:
...
chmod a+x ./runtest.sh ./reboot.py
Error: test raised exception:
HardwareTestHarness instance has no attribute 'planner'
copying attachments...
checking directory /var/log/v7/runs/1/reboot
...

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

How reproducible:
always

Steps to Reproduce:
1. install v7 on RHEL6.1
2. run: v7 run -t reboot
3.
  
Actual results:
ABORT

Expected results:
PASS

Additional info:

Comment 1 Greg Nichols 2011-03-07 13:56:56 UTC
Created attachment 482681 [details]
hardwaretest.py patch fixing traceback on v7 continue

Comment 5 Caspar Zhang 2011-05-01 09:56:01 UTC
This bug does not need a Tech Note because of:

1. A Red Hatter reported it
2. It only happened in an intermediate version.

Comment 6 errata-xmlrpc 2011-05-09 16:15:08 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-2011-0497.html