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.
Description of problem:
- Customer importing Red Hat Repository on Disconnected Red Hat Satellite taking huge time around 5 hours.
Version-Release number of selected component (if applicable):
- Red Hat Satellite Version 6.11.4
How reproducible:
- Try to import Rhel 7 or Rhel 8 AppsSream or Rel 8 BaseOs repository sync will complete but it will take huge time (Approximate 5-6 hours)
Steps to Reproduce:
1. Customer having 36 GB Ram and 8 CPU.
2. Import Huge Red Hat Repository on Disconnected Satellite and observe the time taken to complete.
Actual results:
- Importing huge repository takes 5 hours
Expected results:
- Customer want to improve this and need time similar to Repository sync.
Additional info:
- NA
Verified in 6.14.0 snap 10 (python39-pulpcore-3.22.9-1.1.el8pc.noarch) on a VM with 24 GB RAM, 6 CPUs, 100 GB storage. Unpatched reference VM had exactly the same HW properties.
Steps to verify were practically the same like https://bugzilla.redhat.com/show_bug.cgi?id=2191657#c1, but this time I used smaller repo (rhel-server-rhscl-7-rpms in particular) due to time and storage constraints. Complete export took 17 GB of space, incremental export took 42 MB.
On the unpatched Satellite the complete import took
real 36m23.556s
user 0m5.876s
sys 0m0.740s
and incremental import took
real 29m40.049s
user 0m5.027s
sys 0m0.597s
On the patched Satellite the complete import took
real 25m52.096s
user 0m4.431s
sys 0m0.525s
and incremental import took
real 17m42.946s
user 0m3.224s
sys 0m0.433s
As we can see:
1) the complete import time was improved by ~29 %
2) the incremental import time was improved by ~40 %
3) incremental/complete import time ratio improved from ~82 % to ~69 %.
Given the results I consider the BZ as verified.
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 (Important: Satellite 6.14 security and bug fix 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:6818