Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 176999

Summary: MEMORY test fails due to bug in test script
Product: [Retired] Red Hat Ready Certification Tests Reporter: Rainer Koenig <Rainer.Koenig>
Component: memoryAssignee: Will Woods <wwoods>
Status: CLOSED ERRATA QA Contact: Rob Landry <rlandry>
Severity: medium Docs Contact:
Priority: medium    
Version: 2CC: danny_trinh, hcp-admin, ramalingam.natarajan, richardl
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2006-0284 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-05-08 09:37:37 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
Fixed MEMORY test for rhr2-2.0 none

Description Rainer Koenig 2006-01-05 00:12:08 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.8) Gecko/20050517 Firefox/1.0.4 (Debian package 1.0.4-2)

Description of problem:
Installed rhr2-2.0 on a test machine and did the MEMORY test. Result was that the test failed. 



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

How reproducible:
Always

Steps to Reproduce:
1. Install RHEL4
2. Install rhr2-2.0 test suite
3. Run MEMORY test
  

Actual Results:  Test interface reported error after the test.

Expected Results:  No error.

Additional info:

I had a look at the output.log of the MEMORY test. It dies here:
Line# 59:  echo "Starting RHTS memtest"
Line# 60:  cp $EXTERNALS/bin/{memtst,memtest.sh} .

The problem is that the cp in line 60 fails because memtest.sh is not under $EXTERNALS/bin/
Doing a rpm -ql rhr2-2.0 | grep memt shows:
/usr/share/rhr/external/bin/memtst
/usr/share/rhr/external/memtest.sh

A workaround for this is create a hard link in /usr/share/rhr/external/bin for memtest.sh.
Comment 1 Will Woods 2006-01-12 15:54:18 EST
I've confirmed this problem and committed a fix to CVS; this bug will be fixed
in the next version of rhr2.

That workaround is acceptable, but I strongly recommend running MEMORY2 instead.
Comment 2 Will Woods 2006-01-12 16:10:09 EST
Created attachment 123138 [details]
Fixed MEMORY test for rhr2-2.0
Comment 3 Will Woods 2006-01-12 16:12:19 EST
Could you please try the above MEMORY test to confirm that it solves the
problem? Just copy it to /usr/share/rhr/tests/MEMORY and run a MEMORY test.
Comment 4 Will Woods 2006-01-31 13:16:32 EST
*** Bug 179136 has been marked as a duplicate of this bug. ***
Comment 5 natarajan 2006-03-13 01:42:05 EST
(In reply to comment #4)
> *** Bug 179136 has been marked as a duplicate of this bug. ***

Hi,
sorry for intefernce,
i faced same problem what desribed above and i used fixed memory script for 
running memory test. now its working fine. thanx for all who given me solution.
Comment 8 Red Hat Bugzilla 2006-05-08 09:37:37 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2006-0278.html
Comment 9 Red Hat Bugzilla 2006-05-08 09:37:37 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2006-0284.html