Description of problem:
Network test consistently fails during the first test cycle of both eths.
Version-Release number of selected component (if applicable):
rhel5 (01/5--snap shot 6)
SUT: install OS, install hts, "hts plan" "hts certify --test network --server <ip>"
Network Server (1 active NIC): install OS, install hts, "hts server start"
Fails after bandwidth test (see attached log).
It should passes given the instructions.
Created attachment 145404 [details]
output file from an hts network test run
Please verify the test server is running via "hts server status" on the Test Server.
Also, Could you check the part of the network test that failed via "tcp_lat
The test server was restarted a few times before random network runs. Here is
an output from the current server with the status command.
"python network.py server status
rpc.mountd (pid 4143) is running...
nfsd (pid 4137 4136 4135 4134 4133 4132 4131 4130) is running...
rpc.rquotad (pid 4109) is running...
httpd (pid 4188 4187 4186 4185 4184 4183 4182 4181 4179) is running...
make server RUNMODE=status
Could you give more detail on the exact usage of the tcp_lat parameter in the
Sorry, that's "tcp_lat", so on the client, it would be:
> tcp_lat <server ip or hostname>
lat_tcp gave a 100.8524microseconds result.
Created attachment 145699 [details]
hts network log
Created attachment 145701 [details]
tee'ed output from hts network test
The test is getting farther, now. It is now failing to mount an nfs directory.
The log indicates that the test fails, but an "hts print results" gives a false
The logging process is still over-writing every eth result, but the final one.
Notice this in my attachments (hts network log vs. tee'ed output from hts
(In reply to comment #8)
> The logging process is still over-writing every eth result, but the final one.
> Notice this in my attachments (hts network log vs. tee'ed output from hts
> network test).
The logs from each run are saved in the results (/var/hts/results.xml), and
you can print them via:
hts print --test network --report full
Ahh, I see.
For some reason my server wasn't making/exporting my nfs share. Once I manually
set that up the test ran perfectly.
We are still seeing the initial behavior where the network test fails
pre-maturely. It passes occasionally, but more consistently fails. Could you
open this back up to keep visibly on the network test.
Re-opening per comment 11.
Please attach test results for failed cases.
You can close this issue, it is not being seen anymore.