|Summary:||rhr-net-1.7-7 always fails (RHL 7.2)|
|Product:||[Retired] Red Hat Ready Certification Tests||Reporter:||Glen A. Foster <glen.foster>|
|Component:||net||Assignee:||Chris Kloiber <ckloiber>|
|Status:||CLOSED RAWHIDE||QA Contact:|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2002-04-26 15:51:01 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
Description Glen A. Foster 2002-04-15 14:55:34 UTC
Description of Problem: Regardless of what hardware (all HP, of course :-) I run the network certification test on, the test reports FAILED. Version-Release number of selected component (if applicable): # rpm -qa | grep rhr rhr-interact-1.7-7 rhr-core-1.7-7 rhr-auto-1.7-7 How Reproducible: 100% (always) Steps to Reproduce: 1. install rhr packages 2. edit /etc/rhr.conf (don't touch the eth0 config, though) 3. run redhatready and select only the network test Actual Results: FAILED results every time. Experimenting with the code in /etc/init.d/rhr_functions shows that the lines NOT being filtered out are: Finished 256 requests Finished 256 requests Finished 256 requests Finished 256 requests Finished 256 requests Expected Results: I would expect to be filtered out... e.g., they appear normal since there's no configuration changes or anything special added about the network tests. I propose as a solution, to add to /etc/init.d/rhr_functions: grep -iv "Finished [0-9]* requests" | ... to the output-filtering algorithm on lines 91-105. Additional Information: Not to be aggressive or anything about this issue, but does every 7.2 system fail certification like this, or am I doing something wrong (or missing something like a test-script upgrade)?
Comment 1 Glen A. Foster 2002-04-15 15:39:56 UTC
Hi Chris, I don't know if this is really yours or not to own; but your name is 100% better than Jeff Abbott's (the original assignee).
Comment 3 Rob Landry 2002-04-23 18:23:02 UTC
I've updated the rhr_functions scripts to also exclude the "Finished blah requests" lines. ab has changed and now prints just those three lines to stderr for some reason leaving the remaining output on stdout. The X detection has been updated as well as the tape test (cat could take all of the ram away from the system (or at least to the point that cat couldn't claim anymore) so this has been fixed.
Comment 4 Glen A. Foster 2002-04-26 15:50:54 UTC
Fix verified on my system. Thanks, Rob!
Comment 5 Glen A. Foster 2002-08-15 16:09:14 UTC
Closing bug (since Rob didn't do it :-)