| Summary: | FEAT: v7 certify should support component mode | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] Red Hat Hardware Certification Program | Reporter: | Rob Landry <rlandry> | ||||||
| Component: | Test Suite (harness) | Assignee: | Greg Nichols <gnichols> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Caspar Zhang <czhang> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 1.5 | CC: | czhang, gbai, qcai, rlandry | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| URL: | https://fedorahosted.org/v7/ | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: |
An new feature has been added to v7 1.5 that `v7 certify` command now supports component mode, a user can use '--device' and '--udi' options to certify all tests with same device name or udi one-time.
|
Story Points: | --- | ||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2012-06-05 21:37:05 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 767775, 773756 | ||||||||
| Attachments: |
|
||||||||
Ideally, "v7 certify --device" would run all the required tests on the device that have not yet passed, while "v7 run --device" runs/reruns all the tests for the device (This already works in v7 1.4). Are "required" tests also added, per-run: info, suspend (for systems with battery power) ? Created attachment 558348 [details]
hardwaretest.py patch to provide component certification command via --device and --udi options
Created attachment 558349 [details]
certificationtest.py patch to provide device filtering method
(In reply to comment #1) > Ideally, "v7 certify --device" would run all the required tests on the device > that have not yet passed, while "v7 run --device" runs/reruns all the tests for > the device (This already works in v7 1.4). Makes sense. > > Are "required" tests also added, per-run: info, suspend (for systems with > battery power) ? Yes, I think so.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
An new feature has been added to v7 1.5 that `v7 certify` command now supports component mode, a user can use '--device' and '--udi' options to certify all tests with same device name or udi one-time.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2012-0711.html |
Description of problem: "v7 certify --device {foo}" would be useful if it ran all of the relevant device tests. Expected results: Most devices are fairly self contained 1 device:1 test (network for example); however cpu's span a series of tests that don't usually take device classes. This command would allow for a vendor to certify either type based on device instead of system. This is useful for leverage pool case where a vendor may certify a series of components that are used in multiple systems. Allowing for this would provide continuity.