Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

Verified with Sat 6.5 snap 24.

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

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