Bug #30916: Foreman doesn't start with Puma 5.0 - Foreman

Actions

Copy link

Bug #30916

closed

Foreman doesn't start with Puma 5.0

Added by Evgeni Golov almost 4 years ago. Updated almost 4 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Category:

Packaging

Target version:

Difficulty:

Triaged:

Bugzilla link:

Pull request:

https://github.com/theforeman/foreman/pull/8021, https://github.com/theforeman/foreman/pull/8022, https://github.com/theforeman/foreman/pull/8023

Fixed in Releases:

2.1.4, 2.2.0

Found in Releases:

Red Hat JIRA:

Description

I've seen this while using the 2.1.3 container, but am pretty sure this would apply to other versions and deployments too when using Puma 5.0:

=> Booting Puma
=> Rails 6.0.3.3 application starting in production 
=> Run `rails server --help` for more startup options
2020-09-25T07:54:30 [W|app|] Creating scope :completer_scope. Overwriting existing method Location.completer_scope.
2020-09-25T07:54:30 [W|app|] Creating scope :completer_scope. Overwriting existing method Organization.completer_scope.
2020-09-25T07:54:34 [I|app|] No new seed file updates found. Skipping
Exiting
bundler: failed to load command: bin/rails (bin/rails)
LoadError: cannot load such file -- /home/foreman/vendor/ruby/2.6.0/gems/puma-5.0.0/lib/puma/puma_http11