Bug 1673447
Summary: | Capsule sync planning in foreman-tasks sometimes takes too long | |||
---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | sthirugn <sthirugn> | |
Component: | Content Views | Assignee: | Ivan Necas <inecas> | |
Status: | CLOSED ERRATA | QA Contact: | Lai <ltran> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 6.3.5 | CC: | bkearney, bwallace, dchaudha, dgross, dvoss, egolov, ehelms, inecas, jentrena, jsherril, ktordeur, mdekan, mmccune, pcreech, pmoravec, rankumar, sajha, trichard | |
Target Milestone: | 6.6.0 | Keywords: | Triaged | |
Target Release: | Unused | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | tfm-rubygem-katello-3.12.0-1 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1684698 1726810 (view as bug list) | Environment: | ||
Last Closed: | 2019-10-22 12:47:16 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-02-07 14:55:46 UTC
Ignore the reproducer steps in the Description of the bug. More testing revealed that the number of repos in the content view directly impacts the performance of the sync. To reproduce this bug consistently: 1. Create a content view with a lot of repos (I had 102 repos) 2. Have two or more capsules 3. Publish/promote Content view and observe the time taken to sync to the capsule(s). You will notice that the capsule sync time increases with the number of content view repos. This bug was cloned and is still going to be included in the 6.4.3 release. It no longer has the sat-6.4.z+ flag and 6.4.3 Target Milestone Set which are now on the 6.4.z cloned bug. Please see the Clones field to track the progress of this bug in the 6.4.3 release. Linking up the first of two issues upstream. I'm not 100% if this will cleanly backport to 6.5, we shall see. We may have to do a 3rd fix based on code that is halfway between 6.4 and upstream master. Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25714 has been resolved. 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 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days |