Bug 217940

Summary: Rhel 5 usb test failed on system with internal hub chip
Product: [Retired] Red Hat Hardware Certification Program Reporter: Garry Wong <garry.wong>
Component: Test Suite (tests)Assignee: Greg Nichols <gnichols>
Status: CLOSED DUPLICATE QA Contact: Will Woods <wwoods>
Severity: medium Docs Contact:
Priority: medium    
Version: 5CC: hcp-admin, richardl
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-12-06 09:32:34 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:
Bug Depends On: 217941    
Bug Blocks:    
Attachments:
Description Flags
hts test logs none

Description Garry Wong 2006-11-30 20:42:19 UTC 
Description of problem:

-Rhel 5 usb test failed on system with additional internal 2.0 hub chip
-However, the usb test passed on system without additional internal 2.0 hub 
such as ProLiant DL360 G5

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

Version-Release number of selected component (if applicable): rhel5 hts 
version 5 release 9

How reproducible:


Steps to Reproduce:
1. Install rhel5 x86 beta2 without Virtualization capability onto system under 
test -ProLiant DL365 G1
2. Install rhel5 x86 beta2 onto network test server
3. Install rhel5 hts version 5 release 9 test suite onto both system under 
test and network test server (with IPV4 status ip address 10.1.1.10)
4. On network test server ---> hts  server start
5. On system under test ----> hts plan ----> hts certify --server 10.1.1.10

  
Actual results: Test failed


Expected results: Test should pass as on ProLiant DL360 G5 server


Additional info: See attached.
Comment 1 Garry Wong 2006-11-30 20:42:20 UTC 
Created attachment 142522 [details]
hts test logs
Comment 2 Garry Wong 2006-12-05 23:38:36 UTC 
This is a dup of bug# 217941. Please clsoe.

Thanks,
Comment 3 YangKun 2006-12-06 09:32:34 UTC 

*** This bug has been marked as a duplicate of 217941 ***