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.
DescriptionRam Nainsingh Tiruwa
2018-11-14 20:58:25 UTC
Description of problem:
satellite installer disables Pulp_max_tasks_per_child in the capsule by default, but it does not disable in the satellite.
satellite 6.3.3
Fresh install system with satellite installed
Ran satellite-installer -scenario=satellite
In capsule server /etc/default/pulp_workers Pulp_max_tasks_per_child is commented
# PULP_MAX_TASKS_PER_CHILD=2
In satellite server /etc/default/pulp_workers Pulp_max_tasks_per_child is uncommented
PULP_MAX_TASKS_PER_CHILD=2
This leads to memory leaks on the capsule server
Verified fix in sat 6.5 snap 11.
Pulp workers is commented by default during satellite install:
# To avoid memory leaks, Pulp can terminate and replace a worker after processing X tasks. If
# left commented, process recycling is disabled. PULP_MAX_TASKS_PER_CHILD must be > 0.
# PULP_MAX_TASKS_PER_CHILD=2
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/RHSA-2019:1222
We removed all instances of the configuration for PULP_MAX_TASKS_PER_CHILD as this configuration is no longer supported as it leads to deadlocks in task processing, see:
https://bugzilla.redhat.com/show_bug.cgi?id=1656340
if you are still seeing PULP_MAX_TASKS_PER_CHILD entries in /etc/default/pulp_workers on a Satellite or Capsule then that bug is not resolved but in our tests and internal lab hosts on fresh installations of Satellite and Capsules there is no more PULP_MAX_TASKS_PER_CHILD setting which is correct.
Going to close this out as CURRENTRELEASE but if you are seeing this configuration entry still, please re-open.