Bug 697846 - info test logs missing when reboot test is run
Summary: info test logs missing when reboot test is run
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Hardware Certification Program
Classification: Retired
Component: Test Suite (harness)
Version: 1.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Greg Nichols
QA Contact: Guangze Bai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-19 12:31 UTC by Greg Nichols
Modified: 2015-02-08 21:36 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-05-09 16:12:07 UTC
Embargoed:

Attachments (Terms of Use)
hardwaretest.py patch to save logs/results.xml after each test completes. (1.07 KB, patch)
2011-04-19 12:34 UTC, Greg Nichols 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0497 0 normal SHIPPED_LIVE v7 bug fix and enhancement update 2011-05-09 16:11:16 UTC

Description Greg Nichols 2011-04-19 12:31:21 UTC 
Description of problem:

When running the reboot test, the info test log output is missing.

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

v7 1.3 R32
Comment 1 Greg Nichols 2011-04-19 12:34:10 UTC 
Created attachment 493181 [details]
hardwaretest.py patch to save logs/results.xml after each test completes.
Comment 5 Caspar Zhang 2011-05-01 10:11:25 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:12:07 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
Note You need to log in before you can comment on or make changes to this bug.