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.
During a content view publish, we fetch packages for errata and package groups to purge empty errata and empty package groups from the resulting repository and then at the end we index content. We could index the content from the new repository (i.e. after filters have been applied within Pulp to create the new repo) and then perform the purging by using the indexed content in our repository instead of going to Pulp for that data.
I have also noticed a performance degradation between 2.4 -> 3.0:
2.4:
Content View with 15000 Packages: 3 minute publish time
3.0:
Content View with 15000 Packages: 5 minute publish time
same hardware, no load
Moving to POST since upstream bug http://projects.theforeman.org/issues/14428 has been closed
-------------
Justin Sherrill
Applied in changeset commit:katello|c74960743169a7dc1410f2bcb3a3df0d6d5d230b.
Verified (I think) in SNAP 12.1
Published a CV with RHEL7+SCL (14000+ packages) and it took ~3 minutes.
In general, publish seems to be much more snappy than it has been in previous composes.
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/RHBA-2016:1501