Bug 479074 - Unusable search options: Device ID, Vendor ID
Summary: Unusable search options: Device ID, Vendor ID
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Spacewalk
Classification: Community
Component: WebUI
Version: 0.3
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jan Pazdziora
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space16
TreeView+ depends on / blocked
 
Reported: 2009-01-06 21:33 UTC by Jason Dobies
Modified: 2011-08-05 12:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-05 12:20:42 UTC
Embargoed:


Attachments (Terms of Use)

Description Jason Dobies 2009-01-06 21:33:49 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:
Seen in both the UI and XMLRPC APIs.

Steps to Reproduce:
1. Navigate to the system search UI
2. Under Hardware Devices, there are options for Device ID and Vendor ID

  
Additional info:
As far as I can see, there is no way to retrieve either of these values in the UI, so these cannot reliably be used without going directly to the database.

Even when I went to the database and attempted to use values, no systems were returned. I tried the following options:

system.search.vendor_id
- the VENDOR_ID column in rhnHwDevice (which is gotten from prop1 in rhnDevice)

system.search.device_id
- the ID column in rhnHwDevice (which is gotten from id in rhnDevice)
- the DEVICE_ID column in rhnHwDevice (which is gotten from prop2 in rhnDevice)

Using the UI, I was unable to find any systems using any of these values. Furthermore, the prop1 and prop2 columns were empty in most cases. 

I might be missing something, but I'm not sure how either of these features are usable.

Comment 1 Jan Pazdziora 2010-11-19 16:03:55 UTC
Mass-moving to space13.

Comment 2 Jan Pazdziora 2011-02-28 19:21:49 UTC
Taking for investigation.

Comment 3 Miroslav Suchý 2011-04-11 07:32:31 UTC
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 4 Miroslav Suchý 2011-04-11 07:36:49 UTC
We did not have time for this one during Spacewalk 1.4 time frame. Mass moving to Spacewalk 1.5.

Comment 5 Jan Pazdziora 2011-07-20 11:50:27 UTC
Aligning under space16.

Comment 6 Clifford Perry 2011-08-05 12:20:42 UTC
This is not a priority for Red Hat's Spacewalk developers and will likely not be completed by Red Hat in the next 2 years. We agree that this is a valid request and something that could be achieved. Since it is minor and no one else other than reporter seems to have noticed I am closing this out as DEFERRED. Feel free to re-open if you wish this re-reviewed. 

Cliff


Note You need to log in before you can comment on or make changes to this bug.