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:
A repository with on_demand policy set that was synchronized only a few days/hours ago takes the same amount of time.
Version-Release number of selected component (if applicable):
Satellite 6.9
How reproducible:
100%
Steps to Reproduce:
1. Sync RHEL7 base channel
2. Wait a few days or hours
3. Sync RHEL7 base channel
Actual results:
First and second sync take about the same amount of time
Expected results:
It should only take a fraction of the time as most of the content was already synced before.
Additional info:
Sync takes about 1h for on_demand of 'Red Hat Enterprise Linux 7 Server RPMs x86_64 7Server' repository the first time and this is pretty much the same time it takes after a few hours/days.
Even the first sync for on_demand repository, should it really take 1h?
Steps to retest:
1. Import manifest
2. Enable rhel7 server, rhel8 baseOS, rhel8 AppStream
3. Sync all repos in step 2
4. Wait a day or a few hours
5. Resync all repos
6. Compare times
Expected:
Resync should have a faster time than the first sync
Actual:
Resync does have a faster time than the first sync
Verified on 6.10_09
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.10 Release), 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-2021:4702