Bug 1673447 - Capsule sync planning in foreman-tasks sometimes takes too long
Summary: Capsule sync planning in foreman-tasks sometimes takes too long
Status: MODIFIED
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Content Views
Version: 6.3.5
Hardware: Unspecified
OS: Unspecified
high
high vote
Target Milestone: Unspecified
Assignee: Ivan Necas
QA Contact: Lai
URL:
Whiteboard:
Keywords: Triaged
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-07 14:55 UTC by sthirugn@redhat.com
Modified: 2019-06-22 03:07 UTC (History)
15 users (show)

(edit)
This has been fixed upstream, and will be delivered in a future release.
Clone Of:
: 1684698 (view as bug list)
(edit)
Last Closed:


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Foreman Issue Tracker 25714 None None None 2019-03-18 13:27 UTC
Foreman Issue Tracker 26079 None None None 2019-03-19 08:24 UTC
Red Hat Knowledge Base (Solution) 3945741 Configure None The capsule sync task's planning stage takes a long time to complete on Red Hat Satellite 6.3. 2019-02-28 11:51 UTC

Description sthirugn@redhat.com 2019-02-07 14:55:46 UTC
Description of problem:
Capsule sync planning in foreman-tasks sometimes takes too long

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

How reproducible:
Always

Steps to Reproduce:
This is so far reported only in large Satellite environments with tens of capsules, tens of thousands of content hosts
1. Publish a content view.
2. Promote the content view to a lifecycle environment which has tens of capsules associated with it, serving a large number of content hosts.
3. Notice in the foreman tasks that the CV sync planning takes a long time (sometimes more than 10 minutes) which causes very high capsule sync times.

Actual results:
The capsule sync task's planning takes too long - sometimes more than 10 minutes.

Expected results:
The capsule sync task's planning should finish quickly.

Additional info:

Comment 6 sthirugn@redhat.com 2019-02-11 20:19:20 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.

Comment 11 Mike McCune 2019-03-01 22:16:34 UTC
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.

Comment 16 Justin Sherrill 2019-03-18 13:27:17 UTC
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.

Comment 18 Bryan Kearney 2019-03-18 22:06:33 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25714 has been resolved.


Note You need to log in before you can comment on or make changes to this bug.