Bug 223468
| Summary: | HTS: network test failed if hts certify --server [ipaddress] was run | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Hardware Certification Program | Reporter: | Garry Wong <garry.wong> |
| Component: | Test Suite (tests) | Assignee: | Greg Nichols <gnichols> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5 | CC: | hcp-admin, wwlinuxengineering |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | hts-5.0-21 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-02-02 03:45:10 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: | |||
| Attachments: | |||
Created attachment 145998 [details]
This test results 3 which network test failed
Created attachment 145999 [details]
This is test results that network test passed
This is test results that network test passed
Created attachment 146000 [details]
This test results 3 which network test failed
Resent test results 3
I ran the network test multiple times on a DL320 G5 using R17. Each time I used "hts certify --test=network --server=10.0.0.127" The test passed the first time and the logs showed results for both nics, but on subsequent attempts using the same command line, the test failed and the logs only showed results for one nic even though results "on screen" showed both nics were tested. (In reply to comment #4) > I ran the network test multiple times on a DL320 G5 using R17. Each time I > used "hts certify --test=network --server=10.0.0.127" The test passed the > first time and the logs showed results for both nics, but on subsequent > attempts using the same command line, the test failed and the logs only showed > results for one nic even though results "on screen" showed both nics were > tested. Please attach these test results. - Thanks! Created attachment 146351 [details]
failing network test run with R17 on DL320G5
Created attachment 146352 [details]
Passing network test run with R17 on DL320G5
Created attachment 146362 [details]
System Log during Test Failure
(In reply to comment #8) > Created an attachment (id=146362) [edit] > System Log during Test Failure > The attached system logs seem to indicate something's amiss during the tests. I can not reproduce problems with settings of the --server option interacting with the --test option. Greg, HP wants to know which server us used. The problem is when you run ALL tests at once by using "hts certify --test network --server 10.1.1.10", the network test failed. BUT if you just run network test itself by using "hts certify --test network --server 10.1.1.10", the network test passed. The system under test is Proliant DL365 or DL360 G5. When you said you could not reprod, which command you used ?"hts certify -- test network --server ipaddress" or "hts certify --test network --server ipadsress" ? Thanks I've duplicated what you've seen, and verified a fix. The test server uses lmbench, and its servers shut down after an hour if there is no activity. Since the full test runs more than an hour before the network portion is run, the lmbench tools have shut down by the time the server runs. We've patched lmbench to remove this "feature", so that it does not shutdown. This version (lmbench-3.0a7-5.EL5) should be available shortly on the Partners site. I verified the version lmbench-3.0a7-5.EL5 and it works. Thanks, |
Description of problem: Network test would fail if "hts certify --server [ipaddress]" was run, but would pass if running by itself with command hts certify --test network -- server [ipaddress] Version-Release number of selected component (if applicable): rhel5 hts R17 How reproducible: Steps to Reproduce: 1. Install rhel5 x64 initial release with Virtualization capability onto system under test -ProLiant DL360 G4 2. Install rhel5 x64 initial release onto network test server 3. Install rhel5 hts version 5 release 17 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 ---> lat_tcp -s ---> hts server start 5. On system under test ----> lat_tcp 10.1.1.10 --> hts plan ----> hts certify --server 10.1.1.10 ----> network test failed (see attached test results 3) 6. On system under test ---> hts certify --test network --server 10.1.1.10 --- > network test passed (see attached test results 4) Actual results: -When using "hts certify --server 10.1.1.10" to run all tests, network test failed -When using "hts certify --test network --server 10.1.1.10" to run network test only, the test passed. Expected results: Should pass either case Additional info: