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.
DescriptionWaldirio M Pinheiro
2016-11-16 16:06:47 UTC
Description of problem:
Customer inform their satellite spend long time to sync all repos on their environment using syncplan, once they have 5 orgs and some locations, customer prefer create his own script and after this, got the same behavior on his script syncing via hammer.
Version-Release number of selected component (if applicable):
6.2.4
How reproducible:
100%
Steps to Reproduce:
1. Enable one repo (red hat enterprise linux 7.2 for example)
2. Sync repo
3. Follow via tasks
At the first time, we expect spend large time, Satellite will download ~14GB, at the second time, there isn't new packages to download or just a few packages, so this process should be faster *~2 min or less*, so customer face 5 min, 10 min, 1h just to say *no new packages* or download like 3 new packages
Actual results:
Pulp spend long time to conclude the sync process
Expected results:
if no new packages, get out faster, if new packages, download and just conclude and not stay processing during a long time after conclude the package files *rpm*
Additional info:
There is an upstream Pulp thread I've started to gather more information related to what I believe is this various from since I encountered it myself. [1] I think the crux of the issue relies around something happening with the 'Purge Duplicates' step that occurs during a sync. I'll report more information related to this as I get any.
[1] https://www.redhat.com/archives/pulp-list/2016-November/msg00030.html
Comment 7Waldirio M Pinheiro
2016-11-25 00:58:57 UTC
Verified in Satellite 6.2.8 Snap 2. Sync times are now significantly reduced, when there are no new packages to pull in. See attached for verification.
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-2017:0447