Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1326941

Summary:	content view publish creates extra metadata generation task, slowing publish time
Product:	Red Hat Satellite	Reporter:	Chris Duryee <cduryee>
Component:	Performance	Assignee:	Chris Duryee <cduryee>
Status:	CLOSED ERRATA	QA Contact:	Roman Plevka <rplevka>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	cwelton, mmccune, rplevka
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/14628
Whiteboard:
Fixed In Version:	rubygem-katello-3.0.0.18-1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-27 09:08:30 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 Chris Duryee 2016-04-13 19:52:45 UTC

Description of problem:

As part of the "run" phase of a Katello repo create, it will tell Pulp to do a publish. This is needed in order to fill in the repo immediately, so consumers don't get a 404 in between the time when the user creates the repo in the web UI, and when Pulp does the publish after unit association.

However, when cloning repos, there's no need to do this extra publish. In fact, it can lead to slowness since there's now two publishes happening instead of one.

Version-Release number of selected component (if applicable): 6.2.0 beta snapshot


How reproducible: every time


Steps to Reproduce:
1. sync a large repo (rhel 6 server is a good one)
2. create CV, add repo, publish CV version

Actual results: YMMV, but this can take about five minutes

Expected results: 3-ish minutes

Additional info: If you perform the publish and look at the tasks list, you'll see a "metadata generate" task owned by foreman_api_admin user. This is the task that should go away for CV version publishes.

Also note: this is one issue related to slow CV publish, but there may be other areas that could use optimization.

Comment 2 Bryan Kearney 2016-04-13 20:03:12 UTC

Upstream bug component is Performance

Comment 3 Bryan Kearney 2016-04-14 14:03:29 UTC

Moving to POST since upstream bug http://projects.theforeman.org/issues/14628 has been closed
-------------
Chris Duryee
Applied in changeset commit:katello|d2df121200636ea86d93bdf5305500646f6863f3.

Comment 4 Roman Plevka 2016-04-18 08:13:42 UTC

VERIFIED
on sat 6.2.0 snap 8.1

there's no 'metadata generate' task for CV publish any more.

<task-id>| | admin | 2016/04/18 08:04:04 | 2016/04/18 08:04:04 | stopped | success | Sync Capsule with Content View
<task-id>| | admin | 2016/04/18 08:02:52 | 2016/04/18 08:04:04 | stopped | success | Publish
<task-id>| | admin | 2016/04/18 08:02:35 | 2016/04/18 08:02:35 | stopped | success | Update
<task-id>| | admin | 2016/04/18 07:58:52 | 2016/04/18 07:58:53 | stopped | success | Sync Repository on Capsule(s)
<task-id>| | admin | 2016/04/18 07:45:18 | 2016/04/18 07:58:54 | stopped | success | Synchronize
<task-id>| | admin | 2016/04/18 07:45:18 | 2016/04/18 07:58:54 | stopped | success | Synchronize
<task-id>| | foreman_api_admin | 2016/04/18 07:44:59 | 2016/04/18 07:45:01 | stopped | success | Metadata generate
<task-id>| | admin | 2016/04/18 07:44:57 | 2016/04/18 07:45:00 | stoppedd | success | Enable
...

Comment 6 errata-xmlrpc 2016-07-27 09:08:30 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-2016:1500