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.
Bug 1419128 - Capsule sync in 6.2 is slower than in 6.1
Summary: Capsule sync in 6.2 is slower than in 6.1
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.2.7
Hardware: Unspecified
OS: Unspecified
medium
medium with 1 vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-03 16:18 UTC by Dennis Kliban
Modified: 2021-04-06 17:53 UTC (History)
19 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 18:05:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Pulp Redmine 2567 0 Normal CLOSED - WONTFIX As a user, I can quickly propogate one package change from one Pulp to another Pulp 2020-12-03 17:11:08 UTC
Red Hat Bugzilla 1388296 0 high CLOSED Regression: Syncing large Library of content from Satellite to Capsule takes hours even if no content changes 2021-06-10 11:37:22 UTC
Red Hat Bugzilla 1442073 0 high CLOSED Syncing puppet repositories from Satellite to Capsule takes hours even if no content changes 2021-06-10 12:11:21 UTC

Internal Links: 1388296 1442073

Description Dennis Kliban 2017-02-03 16:18:50 UTC 
Description of problem:

When syncing a capsule with many repositories that all have the same content, each repository still takes a few minutes to sync. 


How reproducible:

All the time

Steps to Reproduce:
1. Create a LCE in satellite with the RHEL7 repository.
2. Create multiple more LCEs in satellite with RHEL7 repository.
3. Create a capsule that is associated with all the LCEs
4. Sync the capsule



Additional info:

This change in behavior in Satellite 6.2 can be attributed to the change in how Pulp is used on a capsule. Satellite 6.1 used Pulp nodes to perform syncs and publishes on the capsule. Pulp nodes did not require parsing of repository metadata before transmitting any data. Satellite 6.2 uses a natural Pulp sync. This sync requires parsing repository metadata. So even if there is no content to sync, it still takes some time to parse the metadata. 

This issue is related to https://bugzilla.redhat.com/show_bug.cgi?id=1395777
Comment 3 pulp-infra@redhat.com 2017-02-03 23:31:37 UTC 
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 4 pulp-infra@redhat.com 2017-02-03 23:31:40 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 5 Michael Hrivnak 2017-02-05 08:37:20 UTC 
The scope of this problem is limited to mostly the first sync of a new capsule, or the first sync after lots of repos have been added to a capsule, right?

In normal operation for yum repos at least, when most repos do not have any changes, the syncs will finish in just a few seconds because of the repomd.xml serial number optimization.

It should also be noted that while this may cost some extra time on the sync end, we are saving a huge amount of time and storage space on the Satellite itself by no longer publishing node metadata. For most customers, I suspect the net trade-off is a substantial improvement in overall performance.
Comment 6 Michael Hrivnak 2017-02-05 08:38:07 UTC 
I'm moving to the Pulp component since the next steps are for the Pulp team.
Comment 7 Michael Hrivnak 2017-02-05 08:50:09 UTC 
Dennis, what do you think about making this an RFE to make pulp-pulp sync more efficient? That would match the upstream issue.
Comment 13 Bryan Kearney 2018-09-04 18:05:16 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Comment 14 pulp-infra@redhat.com 2020-12-03 17:11:09 UTC 
The Pulp upstream bug status is at CLOSED - WONTFIX. Updating the external tracker on this bug.
Note You need to log in before you can comment on or make changes to this bug.