Bug 360221

Summary:	hts-5.1-3.el5 network tesing didn't work
Product:	[Retired] Red Hat Hardware Certification Program	Reporter:	George Beshers <gbeshers>
Component:	Test Suite (tests)	Assignee:	Red Hat Hardware Certification <hwcert-reviewers>
Status:	CLOSED DUPLICATE	QA Contact:	Red Hat Hardware Certification <hwcert-reviewers>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	5	CC:	jh, jlim, martinez
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:	2007-10-31 15:41:51 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:

Description George Beshers 2007-10-31 14:15:27 UTC

Description of problem:
Tried the latest hts-5.1-3.el5 on RHEL5.1RC2 xen kernel, the network test failed 
due to peth0 couldn't be shut down.  Looked like hts-5.0 can tolerate peth0 not 
being shut down and network test will pass.  But hts-5.1 network test will be 
failed with error messages,
 Error: could not shut down interface peth0
 Error: could not shutdown all other interfaces 

This issue must be solved before we can do RHEL5.1 certification on x86_64
platforms.

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

This happened in RHEL5.1RC2 and it's kernel was 2.6.18-52.el5xen.  To run hts
test, do 'hts certify --test network --server machine1'.  The results in
/var/log/hts/runs/1/network/output.log, which showed the error messages.

How reproducible:
  Systematically.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
  I will try to reproduce the problem at Westford.

Comment 1 Larry Troan 2007-10-31 15:41:51 UTC

I had the same peth0 problem per bug 324921. 

I tried hts-5.1-4.el5.noarch.rpm which Greg N. provided me against the latest
5.1 rc bits and the network test ran fine. Working on certifying a system with
it against the 5.1 GOLD bits.

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