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 1434040

Summary: Offload upload package profile to dynflow executor
Product: Red Hat Satellite Reporter: Mike McCune <mmccune>
Component: Content ManagementAssignee: Shimon Shtein <sshtein>
Status: CLOSED ERRATA QA Contact: Roman Plevka <rplevka>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: akofink, andrew.schofield, aperotti, bbuckingham, bkearney, cduryee, chrobert, daniele, dcaplan, egolov, ehelms, jcallaha, jsherril, kabbott, psuriset
Target Milestone: UnspecifiedKeywords: PrioBumpField, PrioBumpPM, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: scale_lab
Fixed In Version: rubygem-katello-3.0.0.143-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1463805 (view as bug list) Environment:
Last Closed: 2017-08-10 17:02:29 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1353215, 1430554    
Attachments:
Description Flags
Hotfix RPM
none
Updated hotfix RPMs
none
Satellite 6.2.9 hotfix none

Description Mike McCune 2017-03-20 15:32:32 UTC
Right now the controller parses packages JSON and plans the action. The problem is that the planning phase is quite long, so the action stays in memory for a long time. This causes GC to mark the JSON as old, so this parameter will stay in memory for a long time causing memory fragmentation.

Comment 1 Mike McCune 2017-03-20 15:32:36 UTC
Created from redmine issue http://projects.theforeman.org/issues/18682

Comment 2 Mike McCune 2017-03-20 15:32:40 UTC
Upstream bug assigned to sshtein

Comment 4 Eric Helms 2017-03-21 02:29:03 UTC
Created attachment 1264895 [details]
Hotfix RPM

Comment 5 Pradeep Kumar Surisetty 2017-03-21 13:13:18 UTC
*** Bug 1434220 has been marked as a duplicate of this bug. ***

Comment 7 Eric Helms 2017-03-22 03:42:27 UTC
Created attachment 1265287 [details]
Updated hotfix RPMs

Comment 11 Satellite Program 2017-05-03 00:11:59 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18682 has been resolved.

Comment 13 Andrew Kofink 2017-06-09 14:32:12 UTC
Created attachment 1286424 [details]
Satellite 6.2.9 hotfix

This is the hotfix for Satellite 6.2.9

Comment 16 Roman Plevka 2017-08-02 14:16:12 UTC
VERIFIED
for 6.2.11-2

Comment 18 errata-xmlrpc 2017-08-10 17:02:29 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-2017:2466