Bug 471157 - FEAT: catalog should check if the correct kernel variant was used when uploading any result rpm package
FEAT: catalog should check if the correct kernel variant was used when upload...
Product: Red Hat Hardware Certification Program
Classification: Red Hat
Component: Hardware Catalog (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: hwcert-catalog
Depends On:
  Show dependency treegraph
Reported: 2008-11-11 22:33 EST by YangKun
Modified: 2011-06-27 13:04 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-06-27 13:04:01 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description YangKun 2008-11-11 22:33:58 EST
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:

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.

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