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:

Using a package filter with 'original packages' checked causes the publish to take a very long time.  Using hammer this publish even times out.

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

How reproducible:
Always

Steps to Reproduce:
1.  Create a content view with multiple repositories containing 25,000 packages total
2.  Create an include package filter that has 'original packages' checked
3.  Click Publish or publish using hammer

Actual results:
Using hammer this times out, using the web UI it can take a very long time.


Expected results:
It is very quick.


Additional info:

Note that if using hammer, there is a workaround:

in  /etc/hammer/cli.modules.d/foreman.yml

increase the request_timeout option to something above 120, or disable it entirely (-1)

The mentioned timeout above is the timeout of the client. But the timeout is also happening within Satellite 6 processes itself, this is tracked in https://bugzilla.redhat.com/show_bug.cgi?id=1275183

*** This bug has been marked as a duplicate of bug 1275183 ***