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 2191657 - Importing Red Hat Repository Import on Disconnected Red Hat Satellite taking huge time around 5 hours
Summary: Importing Red Hat Repository Import on Disconnected Red Hat Satellite takin...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.11.4
Hardware: x86_64
OS: Linux
high
high
Target Milestone: 6.13.1
Assignee: satellite6-bugs
QA Contact: Vladimír Sedmík
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-28 17:03 UTC by Odilon Sousa
Modified: 2023-05-31 15:28 UTC (History)
9 users (show)

Fixed In Version: pulpcore-3.21.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2170485
Environment:
Last Closed: 2023-05-31 15:28:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github pulp pulpcore issues 3075 0 None closed The same content is imported multiple times in a row 2023-04-28 17:03:26 UTC
Red Hat Issue Tracker SAT-16125 0 None None None 2023-04-28 17:03:26 UTC
Red Hat Issue Tracker SAT-17409 0 None None None 2023-04-28 17:05:44 UTC
Red Hat Product Errata RHSA-2023:3387 0 None None None 2023-05-31 15:28:27 UTC

Comment 1 Vladimír Sedmík 2023-05-15 09:36:44 UTC 
Verified in 6.13.1 snap 1 (python39-pulpcore-3.21.6-1.el8pc.noarch) on a VM with 32 GB RAM, 8 CPU, 500 GB storage. The import times were compared to an unpatched Satellite running on a different VM with same RAM/CPU/storage size.   

Steps to verify:
1) Sync RHEL8 AppStream RPMs repo with immediate download policy and perform 'complete repository' export. The repository contains 29342 packages and export takes 88 GB of space.  
2) Sync it again and perform 'incremental repository' export (no content was added actually, but metadata). The export takes just 78 MB.
3) Copy the exports to the importing Satellites (unpatched and patched). Set the default download policy to immediate and upload manifest.
4) Import the complete data, then import the incremental data, measure the task times.

On the unpatched Satellite the complete import took
real	106m33.193s
user	0m14.962s
sys	0m1.889s

and incremental import took
real	53m3.873s
user	0m8.168s
sys	0m1.022s

On the patched Satellite the complete import took
real	84m22.443s
user	0m13.049s
sys	0m1.731s

and incremental import took
real	28m52.590s
user	0m4.893s
sys	0m0.600s

As we can see:
1) the complete import time was improved by ~21 %
2) the incremental import time was improved by ~46 %
3) incremental/complete import time ratio improved from ~50 % to ~34 %.

Given the results I consider the BZ as verified.
Comment 6 errata-xmlrpc 2023-05-31 15:28:22 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 (Moderate: Satellite 6.13.1 Async Security Update), 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/RHSA-2023:3387
Note You need to log in before you can comment on or make changes to this bug.