| Summary: | infiniband test fails: can't log hardware via udev | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Hardware Certification Program | Reporter: | Greg Nichols <gnichols> |
| Component: | Test Suite (tests) | Assignee: | Greg Nichols <gnichols> |
| Status: | CLOSED NOTABUG | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.6.5 | CC: | bbrock, qcai, rlandry |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-04-03 13:58:06 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: | |
| Bug Depends On: | |||
| Bug Blocks: | 1052374 | ||
|
Description
Greg Nichols
2013-10-25 12:38:34 UTC
Looks like the infiniband device shows up in UDEV as:
<device device-bus="" product="cxgb3_0" udi="/devices/pci0000:00/0000:00:02.0/0000:01:00.0/infiniband/cxgb3_0" source="udev" device-class="">
<property name="SUBSYSTEM">infiniband</property>
<property name="UDEV_LOG">3</property>
<property name="NAME">cxgb3_0</property>
<property name="info.udi">/devices/pci0000:00/0000:00:02.0/0000:01:00.0/infiniband/cxgb3_0</property>
<property name="DEVPATH">/devices/pci0000:00/0000:00:02.0/0000:01:00.0/infiniband/cxgb3_0</property>
</device>
The test is planned based on PCI_CLASS, which doesn't appear. Was this test manually planned?
Do we need to add subsystem infiniband as a plan target? We could. Is this a supported configuration/RHEL release? Yes, it was planned manually. By default it wasn't selected. File as a separate bug? No. via Doug's comments, it seems like it's misconfigured?
> This is cxgb3 and it technically is an iWARP system. You might need to
> modify your setup to work with it.
(In reply to Greg Nichols from comment #5) > No. via Doug's comments, it seems like it's misconfigured? > > > This is cxgb3 and it technically is an iWARP system. You might need to > > modify your setup to work with it. Closing |