Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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:
https://community.theforeman.org/t/slow-products-page-on-2-0/19142/23 has indicated adding this index can lead to significant speed up of products page queries/

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


How reproducible:
always


Steps to Reproduce:
1. Have several products which have been synced
2. Open the products page
3.

Actual results:
It takes long time to load

Expected results:
It should load faster

Additional info:

The attached fix can reduce the load times quite drastically, see the thread on discourse. That's why I'd like to propose this for 6.8

*** Bug 1846310 has been marked as a duplicate of this bug. ***

*** Bug 1846312 has been marked as a duplicate of this bug. ***

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

Verified on Satellite 6.8 snap 9 using the export analyze query from the associated foreman.community discussion, the index_tasks_locks_on_task_id_resource_type_and_resource_id has been added and is applied

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 (Important: Satellite 6.8 release), 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-2020:4366