Bug 218104 - Rhel 5 hts Network test failed
Rhel 5 hts Network test failed
Status: CLOSED CURRENTRELEASE
Product: Red Hat Hardware Certification Program
Classification: Red Hat
Component: Test Suite (tests) (Show other bugs)
5
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Greg Nichols
Greg Nichols
:
: 219755 (view as bug list)
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-12-01 15:09 EST by Garry Wong
Modified: 2008-07-16 17:56 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-01-19 19:48:57 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Test results (967.05 KB, application/octet-stream)
2006-12-01 15:09 EST, Garry Wong
no flags Details
Attached is the network test log with running your two commands. (8.55 KB, application/octet-stream)
2006-12-04 16:46 EST, Garry Wong
no flags Details
network test log (40.18 KB, application/octet-stream)
2006-12-05 17:11 EST, Garry Wong
no flags Details
hts submit log (848.06 KB, application/octet-stream)
2006-12-06 15:02 EST, Garry Wong
no flags Details
hts 14 test logs (4.11 MB, application/octet-stream)
2007-01-03 15:35 EST, Garry Wong
no flags Details
hts r17 network test result (2.04 MB, application/octet-stream)
2007-01-19 11:28 EST, Garry Wong
no flags Details
test results from passing network test with R17 (1.79 MB, application/octet-stream)
2007-01-19 11:33 EST, Gregory Feiner
no flags Details
failing network test run with R17 (2.95 MB, application/octet-stream)
2007-01-19 11:48 EST, Gregory Feiner
no flags Details

  None (edit)
Description Garry Wong 2006-12-01 15:09:42 EST
Description of problem:

Rhel 5 hts Network test failed 

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 --test network --
server 10.1.1.10
 
Actual results: Test failed


Expected results:Test should pass


Additional info: See attached test results
Comment 1 Garry Wong 2006-12-01 15:09:44 EST
Created attachment 142612 [details]
Test results
Comment 2 Greg Nichols 2006-12-04 14:39:04 EST
Changed to correct product.
Comment 3 Greg Nichols 2006-12-04 14:50:25 EST
More information is needed:

Was the Firewall enabled on either the system under test,  or the test server?

Do lmbench tests run from the command-line?

On the Test server, run lat_tcp -s
On the system under test, run tap_tcp <server ip address>

Thanks! 


Comment 4 Garry Wong 2006-12-04 15:53:26 EST
I got the return message bash: tap_tcp : command not found when I did "tap_tcp 
10.1.1.10" on the system under test. Please advise.

Thanks,

 
Comment 5 Greg Nichols 2006-12-04 15:55:57 EST
Sorry, that should have been 'lat_tcp'.
Comment 6 Garry Wong 2006-12-04 16:46:49 EST
Created attachment 142777 [details]
Attached is the network test log with running your two commands.
Comment 7 Garry Wong 2006-12-04 16:49:33 EST
With running your two commands, I got the test passed when I did hts print --
summary or --last. But the test is short and the output.log showed errors, see 
attached.

Thanks,
Comment 8 Greg Nichols 2006-12-05 14:46:19 EST
From the output log: 

testing nfs using 10.1.1.10...
Copying 10 x 1000 mbit files to/from 10.1.1.10
mount -o rw,intr,rsize=32768,wsize=32768,udp 10.1.1.10:/var/hts/export
/tmp/tmpFOVInhnfsdir
Mount command FAILED - returned 8192

So, it looks like the system under test failed to mount the directory 
from the test server.  What is the output from "hts server start" when
run on the test server?   Also, does the mount command work when
executed manually?
Comment 9 Garry Wong 2006-12-05 16:10:55 EST
1) The output from "hts server start" when run on the test server:
   Starting NFS services OK
   Starting NFS quotas OK
   Starting NFS daemon OK
   Starting NFS mountd OK
   Starting httpd:     OK

2) When I executed manually "mount -o rw,intr,rsize=32768,wsize=32768,udp 
10.1.1.10:/var/hts/export/tmp/tmpFOVInhnfsdir" I got message: mount: can't 
find 10.1.1.10:/var/hts....... in /etc/fstab or /etc/mtab.

Also I could not this dir ----> /var/hts/export

Thanks,
Comment 10 Garry Wong 2006-12-05 17:09:04 EST
I rebooted both system under test and test server. And re ran your two 
commands and the network test with command: hts certify --test network --
server 10.1.1.10. The test passed on both nics, but in the log, it seems just 
one nic to be tested. See attached rhel5networkoutput.log.

Thanks,
Comment 11 Garry Wong 2006-12-05 17:11:17 EST
Created attachment 142895 [details]
network test log
Comment 12 Greg Nichols 2006-12-06 10:28:03 EST
Please attach the full results produced via "hts submit".

Thanks!
Comment 13 Garry Wong 2006-12-06 15:02:42 EST
Created attachment 142982 [details]
hts submit log

Attached is network test log created by hts submit.

Thanks,
Comment 14 Garry Wong 2006-12-06 16:02:56 EST
What is the correct command to run network eth0 and eth1 seperately instead of 
using command hts certify --test network -- <test server ip address>?

Thanks,

Comment 15 Greg Nichols 2006-12-07 14:43:28 EST
(In reply to comment #9)

> 
> 2) When I executed manually "mount -o rw,intr,rsize=32768,wsize=32768,udp 
> 10.1.1.10:/var/hts/export/tmp/tmpFOVInhnfsdir" I got message: mount: can't 
> find 10.1.1.10:/var/hts....... in /etc/fstab or /etc/mtab.
> 
> Also I could not this dir ----> /var/hts/export
> 
> Thanks,

The hts test server was not creating /var/hts/export in
some circumstances.

Fixed in R14.
Comment 16 Greg Nichols 2006-12-19 12:27:13 EST
*** Bug 219755 has been marked as a duplicate of this bug. ***
Comment 17 Greg Nichols 2007-01-03 11:14:20 EST
Please retest with HTS release 14 or later.
Comment 18 Garry Wong 2007-01-03 11:39:04 EST
I retested with hts R14. when running hts print --last, it indicated the test 
passed on both nics (the SUT has two nics), but in the log, it showed just 
one nic was being tested.

Thanks, 
Comment 19 Irina Boverman 2007-01-03 12:22:50 EST
Reopening based on above comments. Please provide us with the log file
referenced in #18.
Comment 20 Chris Williams 2007-01-03 12:31:49 EST
Garry,

Can you please provide the log requested in comment#19?
Comment 21 Garry Wong 2007-01-03 15:35:59 EST
Created attachment 144733 [details]
hts 14 test logs

Attached is hts 14 network test log.

Thanks,
Comment 22 Greg Nichols 2007-01-09 16:12:14 EST
The --last flag was being ignored - this if fixed in R16.  Otherwise, the
attached test logs show that in run number 1, both network interfaces were run
and passed.

Comment 23 Garry Wong 2007-01-17 13:06:05 EST
 ProLiant DL360 G5 and ProLiant DL365 were system under test to be used. 
Comment 24 Gregory Feiner 2007-01-19 11:18:36 EST
Network test is working for me on the DL320 G5 with R17.
Comment 25 Garry Wong 2007-01-19 11:26:58 EST
In hts 17, the resuls also indicated two nics passed network test. But in the 
output.log appears only eth0 test result was logged. 
Comment 26 Garry Wong 2007-01-19 11:28:26 EST
Created attachment 146001 [details]
hts r17 network test result
Comment 27 Gregory Feiner 2007-01-19 11:33:01 EST
Created attachment 146004 [details]
test results from passing network test with R17
Comment 28 Gregory Feiner 2007-01-19 11:48:12 EST
Created attachment 146009 [details]
failing network test run with R17
Comment 29 Gregory Feiner 2007-01-19 11:51:40 EST
So in comment 26-27 I had done a fresh OS and kit install.  Then I ran the 
cdrom test by itself and then the network test by itself.  Then I peformed a 
submit.  When I run the network test again, it fails and only results for one 
nic get logged.  These results are in comment 28.  Be aware that after the 
network test passed the first time and I did the submit, then I could no 
longer run any tests.  Every attempt to run a test resulted in the error 
below.  I had to rerun "hts plan" before I could run any tests again.

traceback (most recent call last):
  File "/usr/bin/hts", line 113, in ?
    success = hts.do(args)
  File "/usr/lib/python2.4/site-packages/hts/hardwaretest.py", line 67, in do
    return self.doCertify()
  File "/usr/lib/python2.4/site-packages/hts/hardwaretest.py", line 241, in 
doCertify
    tests = self.certification.getTests(self.options.test)
AttributeError: 'NoneType' object has no attribute 'getTests'
Comment 30 Garry Wong 2007-01-19 12:21:28 EST
Correction: Both eth0 and eth1 test results now were logged in hts R17.

Note You need to log in before you can comment on or make changes to this bug.