Bug 670989 - v7 test fails with a traceback when saving test log
Summary: v7 test fails with a traceback when saving test log
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Hardware Certification Program
Classification: Retired
Component: Test Suite (tests)
Version: 1.1
Hardware: Unspecified
OS: Linux
low
medium
Target Milestone: ---
: ---
Assignee: Greg Nichols
QA Contact: Guangze Bai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-19 20:51 UTC by D. Marlin
Modified: 2015-02-08 21:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Red Hat Enterprise Linux Server 5 (Tikanga)
Last Closed: 2011-05-09 16:16:37 UTC


Attachments (Terms of Use)
rundocument.py patch fixing error output on saving logs (2.09 KB, patch)
2011-01-19 21:05 UTC, Greg Nichols
no flags Details | Diff
results from test run on rhelrt-4.farm using patched rundocument.py (2.77 MB, application/x-bzip)
2011-01-20 15:34 UTC, D. Marlin
no flags Details


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 D. Marlin 2011-01-19 20:51:48 UTC
Description of problem:
  When manually running v7 tests on an RT test system in the Hunstville board farm I receive an early teermination and traceback.

Version-Release number of selected component (if applicable):
  kernel-rt-2.6.33.7-rt29.49.el5rt
  v7 version 1.3, release 5

How reproducible:
  always

Steps to Reproduce:
1. v7 clean
2. v7 plan --server v7.farm.hsv.redhat.com
3. v7 certify --mode auto
  
Actual results:

    :
Restoring all interfaces...
...finished running ./network.py, exit code=0
</output>
recovered exit code=0
v7-report-result /V7/v7/network PASS /var/log/v7/runs/1/network/output.log
saved to /var/v7/results.xml
saveOutput: /var/log/v7/runs/1/network/output.log
Traceback (most recent call last):
  File "/usr/bin/v7", line 45, in ?
    success = v7.do(args)
  File "/usr/share/v7/lib/v7/hardwaretest.py", line 189, in do
    result = self.commands[self.command]()
  File "/usr/share/v7/lib/v7/hardwaretest.py", line 802, in doCertify
    self._doRun(tests)
  File "/usr/share/v7/lib/v7/hardwaretest.py", line 710, in _doRun
    self.saveOutput(run, returnValue, outputFilePath)
  File "/usr/share/v7/lib/v7/hardwaretest.py", line 1054, in saveOutput
    if not run.setTestOutput(outputFilePath):
  File "/usr/share/v7/lib/v7/rundocument.py", line 178, in setTestOutput
    errors += e.message + "\n"
AttributeError: ExpatError instance has no attribute 'message' 

Expected results:
  no traceback

Additional info:

Comment 1 Greg Nichols 2011-01-19 21:05:24 UTC
Created attachment 474358 [details]
rundocument.py patch fixing error output on saving logs

Comment 2 Greg Nichols 2011-01-19 21:06:28 UTC
Would you mind giving this patch a try?

Comment 3 D. Marlin 2011-01-19 22:05:46 UTC
I applied the patch and started a new test run.  It has already passed the point where it previously failed, so I think the patch addresses this issue.  I will continue to monitor the test run through completion (up to 22 hours) to make sure there are no further problems.

Comment 4 Greg Nichols 2011-01-20 14:12:20 UTC
Could you attach the results.xml from the run?  I suspect there are other issues here, since the traceback is during error processing.

Comment 7 D. Marlin 2011-01-20 15:09:29 UTC
The test is still running.  It should finish later this morning.  I will attach the results when the run is complete.

Comment 8 D. Marlin 2011-01-20 15:34:23 UTC
Created attachment 474478 [details]
results from test run on rhelrt-4.farm using patched rundocument.py

Comment 14 errata-xmlrpc 2011-05-09 16:16:37 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.