Bug 183400 - ltpstress test in CORE2 fails but claims pass
ltpstress test in CORE2 fails but claims pass
Status: CLOSED DUPLICATE of bug 179548
Product: Red Hat Ready Certification Tests
Classification: Retired
Component: rhr2-tests (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Will Woods
Will Woods
Depends On:
  Show dependency treegraph
Reported: 2006-02-28 15:39 EST by Doug Chapman
Modified: 2007-04-18 13:38 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-28 17:36:11 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
output.log from hwtest CORE2 run (1.11 KB, text/plain)
2006-02-28 15:43 EST, Doug Chapman
no flags Details

  None (edit)
Description Doug Chapman 2006-02-28 15:39:20 EST
Description of problem:

The hwtest CORE2 test claims pass even when ltpstress.sh fails due to rsh not
being set up.  Looking at the log file (which I will attach) I see it fails
immediatly and does not do any testing however hwtest is unaware of this.

I do not notice anything in the documentation saying to enable rsh on the system
in order to run hwtest CORE2.  Please let me know if I am incorrect on this
(either way the test should not report PASS if this is not done).

Version-Release number of selected component (if applicable):

How reproducible:
every time

Steps to Reproduce:
1. run hwtest CORE2
2. examine /var/log/rhr/tests/CORE2/0/output.log for failures
Actual results:
failures from ltpstress.sh and hwtest CORE2 reports PASS

Expected results:
either hwtest CORE2 should fail or ltptest.sh should not use rsh

Additional info:
Comment 1 Doug Chapman 2006-02-28 15:43:04 EST
Created attachment 125420 [details]
output.log from hwtest CORE2 run
Comment 2 Will Woods 2006-02-28 17:36:11 EST

*** This bug has been marked as a duplicate of 179548 ***

Note You need to log in before you can comment on or make changes to this bug.