Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1395777 - Pulp spend long time just to check metadata and say *nothing new* or to download a few packages
Pulp spend long time just to check metadata and say *nothing new* or to downl...
Status: CLOSED ERRATA
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Pulp (Show other bugs)
6.2.4
x86_64 Linux
medium Severity high (vote)
: 6.2.8
: Unused
Assigned To: satellite6-bugs
jcallaha
: PrioBumpGSS, Triaged
Depends On:
Blocks: 1388296 1417110
  Show dependency treegraph
 
Reported: 2016-11-16 11:06 EST by Waldirio M Pinheiro
Modified: 2018-09-19 11:11 EDT (History)
17 users (show)

See Also:
Fixed In Version: pulp-rpm-2.8.7.7-1
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1417110 (view as bug list)
Environment:
Last Closed: 2017-03-06 03:34:49 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Sync Result Messages (39.45 KB, text/x-csrc)
2016-11-24 19:58 EST, Waldirio M Pinheiro
no flags Details
Satellite Server November Usage (161.78 KB, application/zip)
2016-11-29 22:03 EST, Waldirio M Pinheiro
no flags Details
verification screenshot (92.95 KB, image/png)
2017-02-13 16:21 EST, jcallaha
no flags Details


External Trackers
Tracker ID Priority Status Summary Last Updated
Pulp Redmine 2457 High CLOSED - CURRENTRELEASE When syncing do not associate units that are already associated to the repo 2017-01-16 16:02 EST
Pulp Redmine 2466 Normal CLOSED - CURRENTRELEASE Remove unnecessary `deepcopy` calls for sync 2017-01-16 16:02 EST
Red Hat Product Errata RHBA-2017:0447 normal SHIPPED_LIVE Satellite 6.2.8 Async Bug Release 2017-03-06 08:23:41 EST

  None (edit)
Description Waldirio M Pinheiro 2016-11-16 11:06:47 EST
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:
Comment 2 Eric Helms 2016-11-21 16:02:57 EST
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 7 Waldirio M Pinheiro 2016-11-24 19:58 EST
Created attachment 1224100 [details]
Sync Result Messages
Comment 13 Waldirio M Pinheiro 2016-11-29 22:03 EST
Created attachment 1226099 [details]
Satellite Server November Usage
Comment 14 pulp-infra@redhat.com 2016-12-01 14:01:22 EST
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 15 pulp-infra@redhat.com 2016-12-01 14:01:26 EST
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 16 pulp-infra@redhat.com 2016-12-02 14:01:15 EST
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
Comment 17 pulp-infra@redhat.com 2016-12-03 20:31:17 EST
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 18 pulp-infra@redhat.com 2016-12-03 21:01:19 EST
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 19 pulp-infra@redhat.com 2016-12-03 21:01:22 EST
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 20 pulp-infra@redhat.com 2016-12-06 13:01:08 EST
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 21 pulp-infra@redhat.com 2016-12-06 13:01:12 EST
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 22 pulp-infra@redhat.com 2016-12-06 16:30:57 EST
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 23 pulp-infra@redhat.com 2016-12-07 12:01:13 EST
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 28 pulp-infra@redhat.com 2017-01-09 21:01:46 EST
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 29 pulp-infra@redhat.com 2017-01-09 21:01:51 EST
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 30 pulp-infra@redhat.com 2017-01-16 16:02:02 EST
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 31 pulp-infra@redhat.com 2017-01-16 16:02:07 EST
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 33 jcallaha 2017-02-13 16:20:18 EST
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.
Comment 34 jcallaha 2017-02-13 16:21 EST
Created attachment 1250029 [details]
verification screenshot
Comment 39 errata-xmlrpc 2017-03-06 03:34:49 EST
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

Note You need to log in before you can comment on or make changes to this bug.