Bug 1330733 - filtering content hosts by simply entering hostname does not return
Summary: filtering content hosts by simply entering hostname does not return
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-26 20:17 UTC by Jan Hutař
Modified: 2019-09-26 13:59 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-12 21:33:38 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Jan Hutař 2016-04-26 20:17:22 UTC
Description of problem:
Filtering content hosts by simply entering hostname into search bar does not return (spinner keeps spinning)


Version-Release number of selected component (if applicable):
satellite-6.2.0-8.2.beta.el7sat.noarch


How reproducible:
always


Steps to Reproduce:
1. Have Satellite with about 6000+ content hosts registered
2. Go to Hosts -> Content Hosts
3. Clcik into the search bar, enter hostname of one of your systems (in my case I have entered "localhost" as one my system is registered as "localhost.localdomain")  and click [Search]


Actual results:
Spinner keeps spinning, after about 3 minutes, there is a tracenack in the production.log:

  ActiveRecord::RecordInvalid: Validation failed: Fact name has already been taken


Expected results:
Should show me the system or tell me that mine search query is invalid

Comment 3 Bryan Kearney 2016-07-26 15:25:24 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 4 Bryan Kearney 2016-07-26 15:29:22 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 6 Bryan Kearney 2017-01-12 21:33:38 UTC
I am no longer seeing this on 6.2.6 with a list of 1000+ content hosts. Closing this out. If you are still seeing this issue, please feel free to re-open with additional information.


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