Bug 1713802
| Summary: | Every capsule sync causes importers/distributors to get updated making an optimized capsule sync a full sync | |||
|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | sthirugn <sthirugn> | |
| Component: | Capsule - Content | Assignee: | Justin Sherrill <jsherril> | |
| Status: | CLOSED ERRATA | QA Contact: | Lukas Pramuk <lpramuk> | |
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | 6.5.0 | CC: | dchaudha, ehelms, jsherril, pcreech, zhunting | |
| Target Milestone: | 6.6.0 | Keywords: | Regression, Triaged | |
| Target Release: | Unused | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | tfm-rubygem-katello-3.12.0.7-1 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1716580 (view as bug list) | Environment: | ||
| Last Closed: | 2019-10-22 12:47:37 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
|
Description
sthirugn@redhat.com
2019-05-24 21:48:48 UTC
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 |