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.

Description of problem:
There is an API on the capsule that Satellite calls to get an idea of how much that capsule is loaded. This endpoint is terribly inefficient, it completely loads all dynflow execution plans and then counts them, leading to the capsule consuming a lot of memory and eventually getting oom-killed.

Version-Release number of selected component (if applicable):
Probably all currently supported version

How reproducible:
Always

Steps to Reproduce:
1. Have a couple of hosts
2. Run a job which generates a medium amount of output on all the hosts
3. Goto 2

Actual results:
Memory consumed by smart-proxy service grows at a significant rate

Expected results:
Memory consumed by smart-proxy only grows somewhat linearly to the size output from the jobs being run.

Additional info:

Bulk setting Target Milestone = 6.15.0 where sat-6.15.0+ is set.

Verified on Satellite 6.15 snap 1, I haven't registered a significant spike in the smart-proxy's memory consumption in the described scenario

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 (Important: Satellite 6.15.0 release), 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-2024:2010