Bug 205658 - rhr2-2.0-3.EL4.i386.rpm requires the tester to edit the test.conf file in order for the CORE test to run.
Summary: rhr2-2.0-3.EL4.i386.rpm requires the tester to edit the test.conf file in ord...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Ready Certification Tests
Classification: Retired
Component: rhr2
Version: 2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Greg Nichols
QA Contact: Will Woods
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-09-07 21:24 UTC by Adam Sheltz
Modified: 2008-07-17 22:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-07-17 22:03:06 UTC
Embargoed:


Attachments (Terms of Use)

Description Adam Sheltz 2006-09-07 21:24:24 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 (CK-IBM) Firefox/1.5.0.6

Description of problem:
The CORE test fails, and /var/log/rhr/tests/CORE/output.log only shows a checksum.  It fails with no obvious error.  We had to edit /usr/share/rhr/tests/CORE script to accurately reflect where the test was breaking. In rhr2-1.1-3.noarch.rpm the CORE test only requires a user to put a source kernel in /tmp directory.  In the newer version, the user has to edit the test.conf file to reflect a source rpm is in /tmp directory.  

I might have overlooked documentation that stated this change as well as others. If so please point out where these changes are documented. 

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


How reproducible:
Always


Steps to Reproduce:
1.Install rhr2-2.0-3.EL4.i386.rpm
2.Run "redhat-ready"
3.Select CORE test.
4.Execute CORE test.


Actual Results:


Expected Results:


Additional info:

Comment 2 Rob Landry 2008-07-17 22:03:06 UTC
rhr2 has been deprecated, closing these remaining bugs as WONTFIX.  Future bugs
against the "hts" test suite should be opened agains the "Red Hat Hardware
Certification Program" product selecting either "Test Suite (harness)" or "Test
Suite (tests)" components.


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