Bug 1001308
Summary: | FEAT: expresscard test should use dmidecode data to plan expresscard test | ||||||
---|---|---|---|---|---|---|---|
Product: | [Retired] Red Hat Hardware Certification Program | Reporter: | Rob Landry <rlandry> | ||||
Component: | Test Suite (tests) | Assignee: | Rob Landry <rlandry> | ||||
Status: | CLOSED ERRATA | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 1.6.5 | CC: | bbrock, gnichols, qcai, rlandry | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | |||||||
: | 1001311 1012070 (view as bug list) | Environment: | |||||
Last Closed: | 2013-11-13 09:56:42 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: | |||||
Embargoed: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 1001233 | ||||||
Attachments: |
|
Description
Rob Landry
2013-08-26 21:00:36 UTC
Created attachment 802418 [details]
patch to use dmidecode as an expresscard slot detection
I couldn't find what object we're storing the dmidecode data in the harness, it didn't look like we were so I just added a new call. This over time should probably just be part of the hardware dictionary object? Also I only added detection but from the output I think we could look for multiple stanza's with express card, and use the count of those as the number of expresscard slots. Unfortunately I have no way to test that as my box only has a single slot
Patch appears to be present, and expresscard at least partially pass. Tests with the USB expresscard pass as expected, tests for pcie on expresscard fail due to lack of a peripheral. Will retry later with a drive attached. 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-2013-1515.html |