Description of problem:
Vendors usually upload testing results run with a wrong kernel. For example, we need to use *hugemem* kernel for multiple cores & >4GB RAM & 32-bit testing. But vendors test their system with smp kernel. These packages will both waste our storage space and work time.
Version-Release number of selected component (if applicable):
All versions until now(including Catalog 5.4 edition)
We can upload testing results with any kind of kernel to our Catalog.
Vendors usually upload useless packages with wrong testing kernel. Reviewers have to explain to them and direct them to our on-line policy again and again.
There are two sub-feature for this issue:
1. Our test plan should display the legal kernel for testing, reviewers is responsible for it. When we make a test plan, we should also declare the required kernel edition.
2. Our Catalog should recognize the illegal kernel testing packages. When vendors try to upload a wrong kernel testing package, Catalog should display a warning notice to him.
This will make our certification work more "Plan Centric".
This should be solved @ the test suite level. The catalog should accept all results for any # of reasons the tests may have been requested.