Bug 150570 - Search for IP within Satellite does not search hardware profile data
Summary: Search for IP within Satellite does not search hardware profile data
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Network
Classification: Retired
Component: RHN/Web Site
Version: rhn360
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Grant Gainey
QA Contact: Red Hat Network Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-08 14:57 UTC by Clifford Perry
Modified: 2008-10-17 20:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-17 20:49:46 UTC
Embargoed:


Attachments (Terms of Use)

Description Clifford Perry 2005-03-08 14:57:52 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113

Description of problem:
While on site with a customer I noticed that attempting to perform a search for a registered systems IP address failed to find it (even when you choose under the advance search for IP Information). It seems that the web search only searches data within rhnServerNetwork and not the rhnServerNetInterface data. The data stored within rhnServerNetInterface is the data gathered about configured interfaces on the physical system during the hardware gather stage of up2date. 

Version-Release number of selected component (if applicable):
RHN Satellite 3.6.6 and RHN Hosted

How reproducible:
Always

Steps to Reproduce:
1. Login to WebUI -> Systems -> Advance Search
2. Field to search:  	IP address
3. Attempt to search for an alias IP of a registered system and fail to find it. Even though when you go to hardware details for that registered system you see that IP address listed. 
  

Additional info:

Comment 1 Amanda Carter 2008-10-17 20:49:46 UTC
This bug has been closed due to inactivity.  Please open a new bug with specific details if this problem is still occurring or if an enhancement is needed.


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