Bug 2244811

Summary:	Capsule API being hit when getting task counts is inefficient
Product:	Red Hat Satellite	Reporter:	Adam Ruzicka <aruzicka>
Component:	Remote Execution	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.13.0	CC:	ahumbe, aruzicka, pcreech, pmendezh, rlavi
Target Milestone:	6.15.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rubygem-smart_proxy_dynflow-0.9.1, rubygem-dynflow-1.7.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-04-23 17:15:19 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Adam Ruzicka 2023-10-18 11:54:38 UTC

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:

Comment 1 Brad Buckingham 2023-10-30 11:29:29 UTC

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

Comment 3 Peter Ondrejka 2023-12-04 15:00:58 UTC

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

Comment 6 errata-xmlrpc 2024-04-23 17:15:19 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 (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