Bug 1547986

Summary:	unqualified search on hostgroup uses large amount of memory
Product:	Red Hat Satellite	Reporter:	Chris Duryee <cduryee>
Component:	API	Assignee:	Marek Hulan <mhulan>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.14	CC:	akarsale, mhulan, mmccune, tstrachota, zhunting
Target Milestone:	Unspecified	Keywords:	FieldEngineering, PrioBumpField, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	foreman-1.11.0.89-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1553880 1553881 (view as bug list)		Environment:
Last Closed:	2018-05-21 20:16:44 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 Chris Duryee 2018-02-22 13:33:26 UTC

Description of problem:

If you have a large number of hostgroups, an unqualified hostgroup search may consume a large amount of memory.

This bug has similar repro steps and symptoms to #1462350. The memory growth as not as severe as it was in 1462350 but can still OOM a system if there are enough passenger processes.

Version-Release number of selected component (if applicable): 6.2.14

Comment 1 Tomer Brisker 2018-02-22 16:09:01 UTC

Connecting redmine issue http://projects.theforeman.org/issues/22642 from this bug

Comment 2 Satellite Program 2018-02-22 17:12:49 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/22642 has been resolved.

Comment 3 Marek Hulan 2018-02-23 07:21:42 UTC

linking also second bug that does not cause such memory consumption but should be probably applied at the same time

Comment 6 Peter Ondrejka 2018-04-23 11:38:08 UTC

Verified on satellite-6.2.15-1.0.el6sat.noarch, no significant spike recorded when doing an unqualified search on 300+ hostgroups

Comment 11 errata-xmlrpc 2018-05-21 20:16:44 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-2018:1672