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 1331476 - Update Katello to use Task Groups
Summary: Update Katello to use Task Groups
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Partha Aji
QA Contact: jcallaha
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-28 15:13 UTC by Justin Sherrill
Modified: 2019-09-25 21:19 UTC (History)
4 users (show)

Fixed In Version: rubygem-katello-3.0.0.38-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:23:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 13566 0 None None None 2016-04-28 16:01:25 UTC

Description Justin Sherrill 2016-04-28 15:13:24 UTC 
This protocol has changed for pulp 2.8 and new runcible.
Comment 1 Justin Sherrill 2016-04-28 15:13:26 UTC 
Created from redmine issue http://projects.theforeman.org/issues/13566
Comment 2 Justin Sherrill 2016-04-28 15:13:28 UTC 
Upstream bug assigned to paji
Comment 3 Justin Sherrill 2016-04-28 15:14:23 UTC 
This was a new feature added in pulp 2.8 that if we use should improve performance for applicability generation
Comment 5 Partha Aji 2016-05-16 14:19:04 UTC 
look at http://projects.theforeman.org/issues/13284 for more information. 

As of pulp 2.8 Errata applicability regeneration returns a different task format. Assume we ask errata applicability information for multiple systems. Pulp 2.6-2.7 would return individual statuses for each system and satellite would track that before saying "task complete". The number to tasks could scale up to 1000s of tasks and get out of hand. 
 However with 2.8 a new summary task is now returned. Sat gets to see a collated report and manage better.
Comment 6 Justin Sherrill 2016-05-16 14:26:05 UTC 
To add a bit of info:


As part of pulp 2.8, errata applicability generation is able to be split across different workers.  To not break backward compatibility this behaviour is not done by default and all applicability is confined to a single worker (just like in 6.1). This behaviour means that if we are generating applicability for 100 systems, there are 100 tasks that have to be checked.  

If a special flag is passed to the applicability generation call, that work is split across many workers and a special task group is returned.  Now katello can just check the one task group status rather than the 100 that were generated and they are done in parallel.
Comment 7 Bryan Kearney 2016-05-25 22:15:57 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/13566 has been closed
Comment 10 jcallaha 2016-06-08 18:43:47 UTC 
Verified in Satellite 6.2 Beta Snap 15.

Performed the following steps:
1. Sync a repo, add it to a content view and publish
2. Assign host to the content view
3. Install errata, from the content view, on the host
4. Re-sync the repo and re-publish the content view
5. Check to see if installed errata still shows for the host
Comment 11 Bryan Kearney 2016-07-27 11:23:20 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:1501
Note You need to log in before you can comment on or make changes to this bug.