Bug 1717700

Summary: Regeneration of ueber certificate is causing optimized capsule sync to perform force full sync every time.
Product: Red Hat Satellite Reporter: Mike McCune <mmccune>
Component: Capsule - ContentAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED ERRATA QA Contact: Lukas Pramuk <lpramuk>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.2CC: bkearney, chrobert, cpatters, dvoss, egolov, inecas, jalviso, ktordeur, mmccune, satellite6-bugs, smane, sshtein, sthirugn, wpinheir, zhunting
Target Milestone: 6.4.4Keywords: PrioBumpField, Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-3.7.0.57-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1705099 Environment:
Last Closed: 2019-07-15 15:10:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Comment 5 Lukas Pramuk 2019-07-11 17:13:59 UTC 
VERIFIED.

@satellite-6.4.4-2.el7sat.noarch
tfm-rubygem-katello-3.7.0.58-1.el7sat.noarch

by the following manual reproducer:


1) Have Satellite & Capsule 6.4.3 installed with custom certs

2) Sync a bunch of large yum repos (rhel7/rhel6 server) on Satellite with the external capsule

3) Trigger capsule sync tasks and note the time

# time hammer capsule content synchronize --id 2

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

4) Upgrade Satellite and Capsule to 6.4.4 candidate

5) Trigger capsule sync tasks and note the time

>>> times [ 29sec, 16sec, 15sec ]  the fix resolves the perf issue (doing optimized syncs)
Comment 7 errata-xmlrpc 2019-07-15 15:10:26 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:1780