Bug 1472734

Summary:	Puppet processes consuming the whole Passenger Process Pool
Product:	Red Hat Satellite	Reporter:	sbadhwar
Component:	Installation	Assignee:	Eric Helms <ehelms>
Status:	CLOSED ERRATA	QA Contact:	jcallaha
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.3.0	CC:	bbuckingham, bkearney, ehelms, jcallaha, jsherril, sbadhwar
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-21 16:42:27 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:
Bug Depends On:
Bug Blocks:	1405533

Description sbadhwar 2017-07-19 09:55:22 UTC

Description of problem:

With Satellite 6.3, the puppet is configured with PassengerMinInstances set to 16(as can be found in /etc/foreman-installer/scenarios.d/satellite-answers.yaml). Since, the default for PassengerMaxPoolSize is 12, the current setting for Puppet, doesn't allow foreman processes to run hence creating huge lag while running some operation that needs to go through foreman.

It will be better if the value for PassengerMinInstances be kept somewhere below the value of PassengerMaxPoolSize so as to allow room for foreman processes to run.

Comment 1 RHEL Program Management 2017-08-01 18:16:27 UTC

Since this issue was entered in Red Hat Bugzilla, the pm_ack has been
set to + automatically for the next planned release

Comment 4 Eric Helms 2017-10-05 18:27:39 UTC

Created redmine issue http://projects.theforeman.org/issues/21225 from this bug

Comment 8 Satellite Program 2017-10-26 16:16:03 UTC

Upstream bug assigned to ehelms

Comment 9 Satellite Program 2017-10-26 16:16:06 UTC

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

Comment 10 jcallaha 2017-11-02 17:58:42 UTC

Verified in Satellite 6.3 Snap 22.

Verified as part of https://bugzilla.redhat.com/show_bug.cgi?id=1405533#c8

Comment 11 Bryan Kearney 2018-02-21 16:40:15 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/RHSA-2018:0336

Comment 12 Bryan Kearney 2018-02-21 16:42:27 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/RHSA-2018:0336