Bug 1881078 - Use Passenger instead of Puma as the Foreman application server
Summary: Use Passenger instead of Puma as the Foreman application server
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: 6.8.0
Assignee: Eric Helms
QA Contact: Devendra Singh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-21 13:57 UTC by Eric Helms
Modified: 2020-10-27 13:09 UTC (History)
1 user (show)

Fixed In Version: foreman-selinux-2.1.2.2-1,satellite-installer-6.8.0.9-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 13:09:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 30866 0 Urgent Closed Enable passenger by default and backport rules 2021-02-16 09:18:30 UTC
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 13:09:24 UTC

Description Eric Helms 2020-09-21 13:57:23 UTC 
Issues related to SSO, tuning and thread safety have been found when using Puma as the application server. The application deployment should be switched back to using Passenger as the application server to bring it on par with Satellite 6.7.
Comment 7 errata-xmlrpc 2020-10-27 13:09:06 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.8 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-2020:4366
Note You need to log in before you can comment on or make changes to this bug.