Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 436458

Summary: [rhr2][RHEL4] - Create Certification giving Error
Product: [Retired] Red Hat Hardware Certification Program Reporter: Satyabrata Maitra <smaitra>
Component: Test Suite (harness)Assignee: Greg Nichols <gnichols>
Status: CLOSED NOTABUG QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: 5CC: llim
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-03-11 05:05:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
rhr2-EL4-ia64-certification-rpm file none

Description Satyabrata Maitra 2008-03-07 11:44:44 UTC 
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):
rhr2

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 11:44:44 UTC 
Created attachment 297175 [details]
rhr2-EL4-ia64-certification-rpm file
Comment 2 Greg Nichols 2008-03-07 13:36:26 UTC 
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 05:05:50 UTC 
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.