Bug 1472734 - Puppet processes consuming the whole Passenger Process Pool
Puppet processes consuming the whole Passenger Process Pool
Status: NEW
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Installer (Show other bugs)
Unspecified Unspecified
unspecified Severity high (vote)
: GA
: --
Assigned To: satellite6-bugs
Katello QA List
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2017-07-19 05:55 EDT by sbadhwar
Modified: 2017-08-15 15:46 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description sbadhwar 2017-07-19 05:55:22 EDT
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 Product and Program Management 2017-08-01 14:16:27 EDT
Since this issue was entered in Red Hat Bugzilla, the pm_ack has been
set to + automatically for the next planned release

Note You need to log in before you can comment on or make changes to this bug.