Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1684653 - Content view publish planning in foreman-tasks sometimes takes too long
Summary: Content view publish planning in foreman-tasks sometimes takes too long
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Content Views
Version: 6.4.2
Hardware: Unspecified
OS: Unspecified
high
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-01 18:50 UTC by sthirugn@redhat.com
Modified: 2019-03-08 15:18 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)
content view publish planning (deleted)
2019-03-01 18:50 UTC, sthirugn@redhat.com
no flags Details

Description sthirugn@redhat.com 2019-03-01 18:50:09 UTC
Created attachment 1539890 [details]
content view publish planning

Description of problem:
Content view publish planning in foreman-tasks sometimes takes too long

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

How reproducible:
Always

Steps to Reproduce:
1.Create a content view with around 100 yum repos
2.Publish the content view

Actual results:
Content View publish task planning takes a long time.  For a similar content view, time taken for publish task planning (see screenshot on where to find the planning time for publish task) are:
Satellite 6.3.5 - 75 seconds
Satellite 6.4.2 - 75 seconds
Note that this test happened with zero client traffic.  Having client traffic to the satellite further increases the planning time.

Because of this hammer cv publish users have to wait for a long time to get the foreman task id back. In the example below, it took almost 2 minutes to get the task id back on a satellite server with no client traffic.

# date; hammer content-view publish --name rhel7cv --organization-id=21 --async; date
Fri Mar  1 13:43:13 EST 2019
Content view is being published with task e1fff9b2-3060-479a-be45-71d3ab54d9e4
Fri Mar  1 13:45:06 EST 2019

Expected results:
CV publish planning should happen faster and the task id for the hammer command should be returned sooner.

Additional info:
A similar bug for CV capsule sync task planning was fixed in BZ1673447


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