Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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.

Bug 1998291

Summary: Change Puma defaults to match recommendations from Puma documentation
Product: Red Hat Satellite Reporter: Eric Helms <ehelms>
Component: InstallationAssignee: Eric Helms <ehelms>
Status: CLOSED ERRATA QA Contact: Devendra Singh <desingh>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.8.0CC: desingh, gtalreja, jjeffers, mmccune, osousa, saydas
Target Milestone: 6.10.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: satellite-installer-6.10.0.7-1.el7sat, foreman-installer-2.5.2.4-1.el7sat,foreman-installer-2.5.2.4-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1998309 (view as bug list) Environment:
Last Closed: 2021-11-16 14:13:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eric Helms 2021-08-26 18:44:47 UTC

Comment 1 Eric Helms 2021-08-26 18:44:50 UTC
Created from redmine issue https://projects.theforeman.org/issues/33277

Comment 2 Eric Helms 2021-08-26 18:44:52 UTC
Upstream bug assigned to ehelms

Comment 3 Bryan Kearney 2021-08-26 20:05:22 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/33277 has been resolved.

Comment 6 Brad Buckingham 2021-09-07 13:07:21 UTC
*** Bug 2001229 has been marked as a duplicate of this bug. ***

Comment 7 Brad Buckingham 2021-09-07 13:08:51 UTC
This bugzilla is required to resolve the behavior observed in bug 2001229.

Comment 10 Devendra Singh 2021-09-13 14:57:20 UTC
Verified on 6.10 Snap18

1- Created the base version of the Satellite setup using 6.9.4 GA template.
2- Checked the thread FOREMAN_PUMA_WORKERS, FOREMAN_PUMA_THREADS_MIN and FOREMAN_PUMA_THREADS_MAX and they were 2, 0, and 16 respectively.

# systemctl cat foreman.service
# /usr/lib/systemd/system/foreman.service
[Unit]
..........
..........
Environment=FOREMAN_PORT=3000
Environment=FOREMAN_PUMA_THREADS_MIN=0
Environment=FOREMAN_PUMA_THREADS_MAX=16
Environment=FOREMAN_PUMA_WORKERS=2

3- Ran the upgrade from 6.9.4 to 6.10.0 Snap18.
4- Upgrade completed successfully.
5- The CPU and Memory of this machine were 20Gig's of RAM and 6 Core CPU.
6- As per the puma documentation, the size of the worker should be a multiplication of 1.5, On this setup, we have 6 cores hence the worker count is 9 correct.

6 * 1.5 = 9

# ps -aux | grep puma
root      1660  0.0  0.0 112812   976 pts/0    S+   10:50   0:00 grep --color=auto puma
foreman  85144  0.2  2.2 944524 463224 ?       Ssl  05:06   0:54 puma 5.3.2 (unix:///run/foreman.sock) [foreman]
foreman  85215  0.0  2.3 982176 473852 ?       Sl   05:07   0:05 puma: cluster worker 0: 85144 [foreman]
foreman  85220  0.0  3.0 1161132 627200 ?      Sl   05:07   0:12 puma: cluster worker 1: 85144 [foreman]
foreman  85226  0.0  3.1 1226588 634132 ?      Sl   05:07   0:14 puma: cluster worker 2: 85144 [foreman]
foreman  85232  0.0  2.3 975180 476036 ?       Sl   05:07   0:05 puma: cluster worker 3: 85144 [foreman]
foreman  85238  0.0  3.1 1207544 639008 ?      Sl   05:07   0:13 puma: cluster worker 4: 85144 [foreman]
foreman  85245  0.0  3.1 1239024 640004 ?      Sl   05:07   0:13 puma: cluster worker 5: 85144 [foreman]
foreman  85247  0.0  3.0 1194188 622320 ?      Sl   05:07   0:12 puma: cluster worker 6: 85144 [foreman]
foreman  85249  0.1  3.4 1232596 699432 ?      Sl   05:07   0:35 puma: cluster worker 7: 85144 [foreman]
foreman  85263  0.0  3.0 1123360 620512 ?      Sl   05:07   0:11 puma: cluster worker 8: 85144 [foreman]

7- Checked the thread  FOREMAN_PUMA_THREADS_MIN and FOREMAN_PUMA_THREADS_MAX and they were equal.

# systemctl cat foreman.service
# /usr/lib/systemd/system/foreman.service
[Unit]
Description=Foreman
..........
..........
[Service]
User=foreman
Environment=FOREMAN_ENV=production
Environment=FOREMAN_HOME=/usr/share/foreman
Environment=FOREMAN_PUMA_THREADS_MIN=5
Environment=FOREMAN_PUMA_THREADS_MAX=5
Environment=FOREMAN_PUMA_WORKERS=9

8- Verified the fixed in version package.

# rpm -qa|grep -e satellite-installer -e foreman-installer -e foreman-installer
satellite-installer-6.10.0.7-1.el7sat.noarch
foreman-installer-2.5.2.4-1.el7sat.noarch

Comment 14 errata-xmlrpc 2021-11-16 14:13:37 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 (Moderate: Satellite 6.10 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-2021:4702

Comment 15 Red Hat Bugzilla 2023-09-15 01:35:47 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days