Bug 1330733

Summary: filtering content hosts by simply entering hostname does not return
Product: Red Hat Satellite Reporter: Jan Hutař <jhutar>
Component: Content ManagementAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bkearney
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-12 21:33:38 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:

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.