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.
DescriptionJustin Sherrill
2015-09-04 14:12:40 UTC
Description of problem:
During content view publish there are a number of 'update schedule' tasks that are executing within the publish task that are not needed. These are setting the schedule on the Library repos.
In addition, whenever publishing any repositories that are being created are having a task spawned off that does a yum metadata publish. At this point the repos are empty so this does not take very long (less than a second), but it can cause many tasks to be spawned.
Version-Release number of selected component (if applicable):
6.1.1
How reproducible:
Always
Steps to Reproduce:
1. Create a product with 5 repos.
2. Add the product to a sync plan
3. Create a content view and add all 5 repos.
4. Publish the content view.
Actual results:
a) within the 'publish' task of the dynflow console you'll see 5 'UpdateSchedule' tasks.
b) Within Monitor > Tasks you will see 5 MetadataGenerate tasks.
Expected results:
You should see neither a) nor b)
Additional info: