Project

General

Profile

Feature #29780

Drop passenger from puppet-foreman

Added by Eric Helms almost 3 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Category:
Foreman modules
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Related issues

Blocks Foreman - Tracker #29777: Drop passenger supportClosed

Associated revisions

Revision 0dc29a37 (diff)
Added by Ewoud Kohl van Wijngaarden almost 2 years ago

Fixes #29780 - Drop Passenger support

With Foreman 2.5, support to run with Passenger (technically
mod_passenger) is dropped in favor of using Puma with a reverse proxy.

This also moves the request headers part of settings.yaml to a concat
fragment to simplify some code.

It keeps in code to remove tfm-rubygem-passenger-native on EL7 which it
previously didn't do, but is nice to do. It doesn't remove mod_passenger
itself since that's not managed in this module.

Revision 7a6bb052 (diff)
Added by Ewoud Kohl van Wijngaarden almost 2 years ago

Refs #29780 - Drop FOREMAN_BIND handling

In Foreman 2.4 FOREMAN_BIND was dropped and now Puma builds bind
statements based on inherited sockets from systemd. That means it's no
longer needed to match them. This gives a lot more freedom.

This PR chooses to remove the foreman.socket override if Apache is not
enabled. This then uses the default ListenStream from the socket, which
happens to be 0.0.0.0:3000 today but we don't really care.

History

#1 Updated by Eric Helms almost 3 years ago

#2 Updated by The Foreman Bot almost 2 years ago

  • Assignee set to Ewoud Kohl van Wijngaarden
  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/puppet-foreman/pull/928 added

#3 Updated by The Foreman Bot almost 2 years ago

  • Fixed in Releases 2.5.0 added

#4 Updated by Ewoud Kohl van Wijngaarden almost 2 years ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF