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 1716580 - Every capsule sync causes importers/distributors to get updated making an optimized capsule sync a full sync
Summary: Every capsule sync causes importers/distributors to get updated making an opt...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Capsule - Content
Version: 6.5.0
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: 6.5.1
Assignee: Justin Sherrill
QA Contact: Lukas Pramuk
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-03 17:08 UTC by Mike McCune
Modified: 2019-10-30 17:07 UTC (History)
2 users (show)

Fixed In Version: tfm-rubygem-katello-3.10.0.48-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1713802
Environment:
Last Closed: 2019-06-20 14:30:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 26907 0 High Closed Every capsule sync causes importers/distributors to get updated making an optimized capsule sync a full sync 2020-07-17 16:22:19 UTC
Red Hat Product Errata RHBA-2019:1581 0 None None None 2019-06-20 14:30:45 UTC

Description Mike McCune 2019-06-03 17:08:35 UTC 
+++ This bug was initially created as a clone of Bug #1713802 +++

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:

--- Additional comment from  on 2019-05-24T21:48:50Z 

Since this bug report was entered in Red Hat Bugzilla, the 'sat-backlog' flag has been set to ? to ensure that it is properly evaluated for release.

--- Additional comment from  on 2019-05-24T21:48:50Z 

Since this issue was entered in Red Hat Bugzilla, the pm_ack has been set to + automatically for the next planned release.

--- Additional comment from  on 2019-05-24T21:53:21Z 

Created attachment 1573070 [details]
proposed_patch

The patch was quickly tested in-house. Provided to Walmart today, yet to be validated in the customer environment.

--- Additional comment from  on 2019-05-24T21:54:55Z 

This bug report has Keywords: Regression or TestBlocker.

Since no regressions or test blockers are allowed between releases, it is also being [proposed|marked] as a blocker for this release.

Please resolve ASAP.

--- Additional comment from  on 2019-05-28T16:39:25Z 

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.

--- Additional comment from  on 2019-05-28T16:41:03Z 

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

--- Additional comment from  on 2019-05-30T20:03:33Z 

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26907 has been resolved.
Comment 4 Lukas Pramuk 2019-06-19 21:12:08 UTC 
VERIFIED.

@satellite-6.5.1-1.el7sat.noarch
tfm-rubygem-katello-3.10.0.48-1.el7sat.noarch

by reproducer described in comment#0:

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

# time hammer capsule content synchronize --id 2

>>> times [ ~4min, 29sec, 28sec ... ] 

3) Upgrade Satellite and capsule to 6.5.0
4) Trigger capsule sync tasks and note the time

>>> times [ ~16min, ~17min, ... ], with 6.5.0 there is performance issue (doing fullsyncs all the time)

5) Upgrade Satellite and capsule to 6.5.1 (candidate)
6) Trigger capsule sync tasks and note the time

>>> times [ 3min32, 34sec, 32sec ... ], the fix resolves the perf issue (optimized syncs performing similarly with 6.4)
Comment 6 errata-xmlrpc 2019-06-20 14:30:43 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, 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/RHBA-2019:1581
Note You need to log in before you can comment on or make changes to this bug.