Bug 436458 - [rhr2][RHEL4] - Create Certification giving Error
[rhr2][RHEL4] - Create Certification giving Error
Product: Red Hat Hardware Certification Program
Classification: Red Hat
Component: Test Suite (harness) (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Greg Nichols
Depends On:
  Show dependency treegraph
Reported: 2008-03-07 06:44 EST by Satyabrata Maitra
Modified: 2008-03-11 01:05 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-03-11 01:05:50 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
rhr2-EL4-ia64-certification-rpm file (14.76 KB, application/x-rpm)
2008-03-07 06:44 EST, Satyabrata Maitra
no flags Details

  None (edit)
Description Satyabrata Maitra 2008-03-07 06:44:44 EST
Description of problem:
When tried to create certification for rhr2 hardware test suite, its given the
following error :-

Error : "Unknown Kernel Unable to determine release from package results."

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

How reproducible:
Always and for all archs could test so far.

Steps to Reproduce:
1. Perform rhr2 testing on ia64, ppc, s390 and s390x archs
2. Collect the result rpm file.
3. Try to create certification on hwcert web page
4. Observe the result

Actual results:
Giving error.

Expected results:
It should successfully create the certification.

Additional info:
Comment 1 Satyabrata Maitra 2008-03-07 06:44:44 EST
Created attachment 297175 [details]
rhr2-EL4-ia64-certification-rpm file
Comment 2 Greg Nichols 2008-03-07 08:36:26 EST
HTS 5.1 should be used for RHEL 4 certifications.  Is there some reason this was
not done?
Comment 3 Satyabrata Maitra 2008-03-11 01:05:50 EDT
Hi Greg

Extremely sorry, Actually this bug has been filed wrongly as hwcert does not
support rhr2, as I know. So, closing this bug for now.

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