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
Created attachment 142612 [details] Test results
Changed to correct product.
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!
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,
Sorry, that should have been 'lat_tcp'.
Created attachment 142777 [details] Attached is the network test log with running your two commands.
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,
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?
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,
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,
Created attachment 142895 [details] network test log
Please attach the full results produced via "hts submit". Thanks!
Created attachment 142982 [details] hts submit log Attached is network test log created by hts submit. Thanks,
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,
(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.
*** Bug 219755 has been marked as a duplicate of this bug. ***
Please retest with HTS release 14 or later.
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,
Reopening based on above comments. Please provide us with the log file referenced in #18.
Garry, Can you please provide the log requested in comment#19?
Created attachment 144733 [details] hts 14 test logs Attached is hts 14 network test log. Thanks,
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.
ProLiant DL360 G5 and ProLiant DL365 were system under test to be used.
Network test is working for me on the DL320 G5 with R17.
In hts 17, the resuls also indicated two nics passed network test. But in the output.log appears only eth0 test result was logged.
Created attachment 146001 [details] hts r17 network test result
Created attachment 146004 [details] test results from passing network test with R17
Created attachment 146009 [details] failing network test run with R17
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'
Correction: Both eth0 and eth1 test results now were logged in hts R17.