Bug 1395777 - Pulp spend long time just to check metadata and say *nothing new* or to download a few packages
Summary: Pulp spend long time just to check metadata and say *nothing new* or to downl...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.2.4
Hardware: x86_64
OS: Linux
medium
high vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: jcallaha
URL:
Whiteboard:
Depends On:
Blocks: 1388296 1417110
TreeView+ depends on / blocked
 
Reported: 2016-11-16 16:06 UTC by Waldirio M Pinheiro
Modified: 2021-04-06 17:54 UTC (History)
20 users (show)

Fixed In Version: pulp-rpm-2.8.7.7-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1417110 (view as bug list)
Environment:
Last Closed: 2017-03-06 08:34:49 UTC
Target Upstream Version:


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


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

Description Waldirio 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:

Comment 2 Eric Helms 2016-11-21 21:02:57 UTC
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-25 00:58:57 UTC
Created attachment 1224100 [details]
Sync Result Messages

Comment 13 Waldirio M Pinheiro 2016-11-30 03:03:55 UTC
Created attachment 1226099 [details]
Satellite Server November Usage

Comment 14 pulp-infra@redhat.com 2016-12-01 19:01:22 UTC
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.

Comment 15 pulp-infra@redhat.com 2016-12-01 19:01:26 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.

Comment 16 pulp-infra@redhat.com 2016-12-02 19:01:15 UTC
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.

Comment 17 pulp-infra@redhat.com 2016-12-04 01:31:17 UTC
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.

Comment 18 pulp-infra@redhat.com 2016-12-04 02:01:19 UTC
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.

Comment 19 pulp-infra@redhat.com 2016-12-04 02:01:22 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.

Comment 20 pulp-infra@redhat.com 2016-12-06 18:01:08 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.

Comment 21 pulp-infra@redhat.com 2016-12-06 18:01:12 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.

Comment 22 pulp-infra@redhat.com 2016-12-06 21:30:57 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.

Comment 23 pulp-infra@redhat.com 2016-12-07 17:01:13 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.

Comment 28 pulp-infra@redhat.com 2017-01-10 02:01:46 UTC
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.

Comment 29 pulp-infra@redhat.com 2017-01-10 02:01:51 UTC
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 21:02:02 UTC
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 21:02:07 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.

Comment 33 jcallaha 2017-02-13 21:20:18 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.

Comment 34 jcallaha 2017-02-13 21:21:05 UTC
Created attachment 1250029 [details]
verification screenshot

Comment 39 errata-xmlrpc 2017-03-06 08:34:49 UTC
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.