Bug 1698876

Summary: Registered Hosts: inefficient google-style filter
Product: Red Hat Satellite Reporter: Lukáš Hellebrandt <lhellebr>
Component: ReportingAssignee: Marek Hulan <mhulan>
Status: CLOSED ERRATA QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.5.0CC: cwelton, inecas, mhulan, oprazak
Target Milestone: 6.5.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: foreman-1.20.1.34-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-14 12:40: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:
Embargoed:
Attachments:
Description Flags
production.log none

Description Lukáš Hellebrandt 2019-04-11 12:25:52 UTC
Created attachment 1554505 [details]
production.log

Description of problem:
When filling a google-style filter while generating the Registered Hosts report, the filtering is done very inefficiently. On my instance (with RHEL channel synced and only two hosts registered), filtering took ~20 minutes.

Version-Release number of selected component (if applicable):
Reproduced on Sat 6.5 snap 23

How reproducible:


Steps to Reproduce:
1. Have a Satellite with RHEL channel synced and some hosts
2. Monitoring -> Reporting Templates -> generate Registered Hosts
3. Fill filter in form "<system_name>" matching some of the systems, submit

Actual results:
Generating takes absurdly long - 20 minutes for 2 systems!

Expected results:
Generating should take reasonable time

Additional info:
production.log attached

Comment 5 Lukáš Hellebrandt 2019-04-17 12:49:27 UTC
Verified with Sat 6.5 snap 24.

With the same configuration, generating with google-style filter was virtually immediate and the results were correct.

Comment 7 errata-xmlrpc 2019-05-14 12:40:38 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:1222