Bug 521964

Summary: Running v7 FV guest tests with mis-named data image file results in python traceback
Product: [Retired] Red Hat Hardware Certification Program Reporter: Gary Case <gcase>
Component: Test Suite (tests)Assignee: Greg Nichols <gnichols>
Status: CLOSED ERRATA QA Contact: Lawrence Lim <llim>
Severity: high Docs Contact:
Priority: high    
Version: 5.3CC: rlandry, tools-bugs, ykun, yoyzhang
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-10-14 13:28:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Errors displayed during test run attempt none

Description Gary Case 2009-09-08 21:25:15 UTC 
Description of problem:
If you run the full virt guest tests in v7 without specifying a network test server, even if you're not running a network test, the tests will fail with a python traceback. I tried both fv_memory and fv_core and received errors on both.


Version-Release number of selected component (if applicable):
v7 1.0-15.el5

How reproducible:
every time

Steps to Reproduce:
1. Install RHEL5.4 x86_64 and v7
2. create a test plan 'v7 plan'
3. Run one of the FV guest tests 'v7 run --test=fv_core'
4. Installer starts downloading guest files, then exits with error (see attached file)
  
Actual results:
Aborted test

Expected results:
Completed test

Additional info:
Comment 1 Gary Case 2009-09-08 21:28:27 UTC 
Created attachment 360137 [details]
Errors displayed during test run attempt
Comment 12 Lawrence Lim 2009-10-04 06:45:28 UTC 
What's the definition of POST in this case?
Comment 13 Greg Nichols 2009-10-05 14:14:04 UTC 
POST means a patch/fix is suggested.

This bug should be in ON_QA.
Comment 14 Lawrence Lim 2009-10-07 16:11:16 UTC 
Moving to VERIFIED as confirmed by gcase in Comment #11.
Comment 17 errata-xmlrpc 2009-10-14 13:28:57 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-2009-1498.html