| Summary: | RFE: support select machine with Subsys Device ID | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Qian Hong <qhong> |
| Component: | scheduler | Assignee: | Bill Peck <bpeck> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 0.8 | CC: | bpeck, dcallagh, kzhang, rmancy, stl |
| 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: | 2012-09-28 02:17:41 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: | |
Subsys device id was added to the web UI in bug 602741 and to <hostRequires/> in bug 731615. |
Description of problem: I found a bug behaviors different on different Subsys Device ID, currently there is no way to query a system by subsys_device_id in XML or Web UI In the coming release of beaker, we can query system by Device Driver in XML. That's really a good news. In Common/bkr/common/test_schema.py , I found an example as: --- snip --- <hostRequires> <device op="=" type="network" bus="pci" driver="e1000e" vendor_id="8086" device_id="10d3" subsys_vendor_id="8086" subsys_device_id="a01f" /> </hostRequires> --- snip --- Hopes searching by subsys_device_id will be really supported. Here is the discussion on beaker irc channel: --- snip --- <fracting> hello, today I found a bug which seems can be reproduced on Machine_A but can't be reproduced on Machine_B . The vendor ID, device ID, subsys vendor ID of Machine_A and Machine_B are the same, only the subsys device ID of them are different. Do we have any method to query a machine by subsys_device_id ? thx a lot :) <stl> fracting: coming soon to a beaker near you... <stl> https://bugzilla.redhat.com/show_bug.cgi?id=731615 <fracting> stl: thx a lot! just check Common/bkr/common/test_schema.py and found an example. cooool! How about search in the web UI? <stl> fracting: you can (already) search by device id etc in the web ui, i think in your case they will show up as separate entries <stl> fracting: what is the device you are looking at now? <dcallagh> can't search by subsys device id though, it seems <dcallagh> which is what fracting needs, i think? <stl> correct <dcallagh> fracting: you could file an RFE in bugzilla for that <stl> but still, there will only be one or two devices that differ only by subsys device id <fracting> stl, dcallagh: thx, here is the device: https://beaker.engineering.redhat.com/devices/view/3570 <stl> i was just looking at e1000 as an example <fracting> I'm a bit confused, could we search by subsys_device_id in web UI now? <stl> ah, sorry, i see. you can only get the list of systems which have it, and you can't see its full device details <fracting> stl: exaclty <stl> fracting: they are all listed on this page, however: https://beaker.engineering.redhat.com/devices/NETWORK?list_tgp_no=8&list_tgp_limit=50&list_tgp_ordering=description <stl> so in that table, you can find the subsys device id you need and get the list of systems with that <fracting> stl: so that's a workround :) I know that, but thanks for your help as well --- snip --- Thank you and go on for the awesome work!