Bug 450654

Summary:	FEAT: checking for boot parameters should be done before checking the kernel
Product:	[Retired] Red Hat Hardware Certification Program	Reporter:	YangKun <ykun>
Component:	Test Suite (tests)	Assignee:	Greg Nichols <gnichols>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	5	CC:	rlandry, xisun
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-09-12 18:04:59 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-06-10 08:54:36 UTC

In the INFO test(hts-5.2-14), checking for boot parameters is added into the end
of the "checkKernel" method. which means, if the kernel is tainted, this method
will return "false" immediately, and the boot parameter checking will be
skipped. This is bad for reviewing. E.g., for those laptops which ships with
ipw3945/4965 wireless NIC and for those machines which uses 3rd party drivers,
we(or the hwcert catalog) can never get the boot parameters from the INFO's
output.log directly.

Can we re-schedule the boot parameter checking before checking the kernel in the
"checkKernel" method or add a new "checkBootParameter" method ?

Regards
-YK

Comment 1 Greg Nichols 2008-06-20 17:05:00 UTC

Fixed kernel checks to continue on failure - HTS 5.2 R17