Bug 1002768

Summary:	FEAT: hwcert-client should indicate why it hasn't defaulted a plan item that is present
Product:	[Retired] Red Hat Hardware Certification Program	Reporter:	Rob Landry <rlandry>
Component:	Test Suite (harness)	Assignee:	Greg Nichols <gnichols>
Status:	CLOSED EOL	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.7	CC:	gnichols, rlandry
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	hwcert-client 1.7.0 R55	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1001807	Environment:
Last Closed:	2020-03-27 15:51:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Rob Landry 2013-08-30 00:13:37 UTC

+++ This bug was initially created as a clone of Bug #1001807 +++

Description of problem:

Currently hwcert-client doesn't plan tests it doesn't need, and this is correct however it leaves it as an exercise for the user to determine why it doesn't think it needs to test something.  It would be helpful if it provided some indicator that a test was skipped for what reason.  This way it would be more clear that it isn't a basic hardware detection issue.

Comment 1 Greg Nichols 2013-09-25 01:09:38 UTC

Committed to R55

Comment 4 Greg Nichols 2013-10-30 18:08:58 UTC

Using hwcert-client 1.7.0 R62

The following tests are recommended to complete the certification:
 1 ->    USB2                  pci0000:00/0000:00:1a.0/usb1        
 2    pp 1GigEthernet em1        pci0000:00/0000:00:02.0/0000:04:00.0/net/em1
 3 ->    1GigEthernet em2        pci0000:00/0000:00:02.0/0000:04:00.1/net/em2
 4 ->    memory                                                    
 5 ->    fv_core                                                   
 6 ->    fv_memory                                                 
 7 ->    fv_network                                                
 8 ->    fv_storage                                                
 9 ->    video                 pci0000:00/0000:00:1c.7/0000:01:00.1
10 ->    storage    host0      host0/target0:0:0/0:0:0:0/block/sda 
11 ->    core                                                      
12 <>    info                                                      
13 ->    kdump      nfs                                            
14 ->    kdump      local                                          
Ready to begin testing? (run|edit|quit) 

Note the "pp" for the network test of em1 - it was left off because it passed before.