Description of problem: When testing for network on RHEL5.1-Server with x86_64 arch for hts-5.1.1, sometimes its FAILs, and sometimes It PASS. Both the .tar file along with all log file and .rpm file and sysreports are attached with this bug. Version-Release number of selected component (if applicable): hts-5.1.1 tree followed - 20070927.0 How reproducible: randomly Steps to Reproduce: 1. 2. 3. Actual results: Its randomly FAILS Expected results: It should be PASS each time Additional info:
Created attachment 214451 [details] network-files for latest run which FAIL, with tree 20070927.0
Created attachment 214461 [details] network-files for prior run which PASS, with tree 20070927.nightly
Both attachments indicate the network test passed. Could you attach /var/log/results.xml for the failing case? Thanks!
Created attachment 219051 [details] RHEL5.1 - results.xml where it FAILS showing, with 20070927.0 tree in latest rest
Actully if both the tests are PASS showing as you said, so, I think the hardware catelog result is not showing perfectly. Because, The PASS or FAIL status, I collected from after creating the certification for both the latest and prior .rpm file. Anyway, the results.xml file for the FAILING Test is attached now, pls suggest. And surprisingly the test, where it was PASS, there the /var/hts/results.xml file is showing empty, no content showing within that file. :(. really do not know the reason. Anyway.. Latest certification number with 20070927.0 tree is - 265328 Prior certification number with 20070927.nightly tree is - 265324 Please see and suggest if there is any confilct with the actual result and the result status showing in hwcert.
Here's the log from the failed network test: Running ./network.py: using test server 10.12.4.144 Interface eth1 is down Bringing up interface eth1 ifup eth1 returned 0 Error: could not restart interface eth1 Error: could not bounce interface eth1 ...finished running ./network.py, exit code=1 So, the test could not bring up the interface eth1. I suspect eth1 was not connected to a network. Can you verify that it was> Thanks!
Hi Greg Is it necessary that eth1 must be connected to a network for all the systems or it must be there in the system active all the time? If not, so, eth1 should FAIL always in such cases. right? In such cases, what to do? Even if eth1 Fails, if eth0 is PASS, should I treat the Network test as PASS? Please inform. Anyway, I will check it once more retesting it and get back to you with result. :)
Greg As I tested it with hts5.1-4 once again, at the time of testing its showing in terminal, that eth1 or eth2 or eth3 (which ever appears in test plan) is FAILED, and suggesting me to check the cable. That means, the cable surely not connected even if the ethernet cards are attached with that system. As I did it on reserved system, not possible for me to check it by person. But seems that, each of these case, the cable not connected. Am i right? Please inform.
Yes, if one of the interfaces was not connected, HTS will fail the network test for that interface, and the hardware catalog will mark the network test as a failure. Closing this as not a bug.