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:
Every capsule sync causes importers/distributors to get updated making an optimized capsule sync a full sync

Version-Release number of selected component (if applicable):
Satellite 6.5.0

How reproducible:
Always

Steps to Reproduce:
1. Create a bunch of (large) yum repos on satellite 6.4 with one or more capsules.
2. Trigger capsule sync tasks and note the time
3. Upgrade Satellite and capsule(s) to 6.5
4. Trigger capsule sync tasks and note the time

Actual results:
6.5 capsule sync took about 4 times more than the 6.4 capsule sync.

Expected results:
capsule sync should be optimal and in line with 6.4 performance.

Additional info:

Note that this happens only on a Satellite/Capsule upgraded from 6.4 to 6.5 and not on the newly installed 6.5 capsules.

Created redmine issue https://projects.theforeman.org/issues/26907 from this bug

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26907 has been resolved.

VERIFIED.

@Satellite-6.6.0 Snap11
tfm-rubygem-katello-3.12.0.7-1.el7sat.noarch

by reproducer described in comment#0:

1) Sync a bunch of large yum repos (rhel7/rhel6 server) on Satellite with one external capsule
2) Trigger capsule sync tasks and note the times

>>> times [ 40min, 19sec, 16sec ... ], after one full sync optimized syncs start to take place

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/RHSA-2019:3172