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.

Description of problem:

  The "Applicable Errata" report template fails when run against a large number of hosts.  (Approximately 17,000).   It runs for about 12 hours, until it finally ends with a "500 Internal Server error".  (Maybe that 12 hours is a timeout wall?)

  When smaller numbers 

Version-Release number of selected component (if applicable):

  Red Hat Satellite 6.5.2

How reproducible:
Steps to Reproduce:
1.   In the WebUI:  "Monitor"->"Report Templates"->"Applicable Errata"
2.   In the Hosts Filter, specify a search string to match a large number of hosts.  Leave errata filter blank
3.   Submit

Actual results:

   Small numbers return in reasonable amount of time
   Large searches take impossibly long to report

Expected results:

   Reports generate or at least complete in reasonable amount of time.  (i.e. not erroring after 12 hours of waiting to return)

Created redmine issue https://projects.theforeman.org/issues/29970 from this bug

Upstream bug assigned to oezr

Upstream bug assigned to oezr

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/29970 has been resolved.

This was missaligned upstream as it was not closed by the merge and only got aligned to 3.2, but actually landed in 2.3, so it is already included in Sat 6.9

We have considered this BZ during a triage and since some work has already been done and no feedback has been received, we consider the work being done enough.