Bug 1881078

Summary:	Use Passenger instead of Puma as the Foreman application server
Product:	Red Hat Satellite	Reporter:	Eric Helms <ehelms>
Component:	Installation	Assignee:	Eric Helms <ehelms>
Status:	CLOSED ERRATA	QA Contact:	Devendra Singh <desingh>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.8.0	CC:	okhatavk
Target Milestone:	6.8.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 13:09:06 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 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