Bug 471157

Summary: FEAT: catalog should check if the correct kernel variant was used when uploading any result rpm package
Product: [Retired] Red Hat Hardware Certification Program Reporter: YangKun <ykun>
Component: Hardware CatalogAssignee: hwcert-catalog
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.2CC: averma, rlandry, sdenham, tfu, xiqin
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: 2011-06-27 17:04:01 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:

Description YangKun 2008-11-12 03:33:58 UTC
Description of problem:

We now have a very clear requirement in our policy on what kernel variant should be used when testing on a certain machine, please refer to the "Kernels" section:
    https://hardware.redhat.com/doc/sect-Hardware_Certification_Policy_Guide-Policies-Software_Policies.html

When someone uploads a result package, the catalog should check if the correct kernel variant was used. Please notice that I'm not talking about the kernel version numbers, I'm talking about the kernel variants, e.g: the normal "kernel" or the "kernel-smp" or the "kernel-hugemem" or the "kernel-largesmp" for RHEL4 certifications.

The catalog should notify the person who's uploading the package and reject the result rpms from a "wrong" kernel variant(may direct he/she to our online policy on the kernel requirement list as well). At least the catalog should add a special "mark" to these packages if we allow vendors to upload such result rpms from a "wrong" kernel variant.

It is do-able for the catalog to check this. Just need to check the CPU type(ARCH and several flags) and the CPU numbers and the MEMORY size from the INFO test.

Currently reviewers have to manually check this for every result rpm, which is time wasting and a bit annoying. It will be great if the catalog can do this for us.