Actions
Bug #30916
closedForeman doesn't start with Puma 5.0
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Packaging
Target version:
-
Difficulty:
Triaged:
No
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
Updated by Evgeni Golov almost 4 years ago
Seems to be a Puma bug, which is fixed in their git master: https://github.com/puma/puma/pull/2381
The PR says it only happens on EL8, while our Containers run on Fedora, but I guess still pretty close.
Updated by The Foreman Bot almost 4 years ago
- Status changed from New to Ready For Testing
- Assignee set to Evgeni Golov
- Pull request https://github.com/theforeman/foreman/pull/8021 added
Updated by The Foreman Bot almost 4 years ago
- Pull request https://github.com/theforeman/foreman/pull/8022 added
Updated by The Foreman Bot almost 4 years ago
- Pull request https://github.com/theforeman/foreman/pull/8023 added
Updated by Evgeni Golov almost 4 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset foreman|6390032135e3949af51bb60790973a6b92d78414.
Updated by Tomer Brisker almost 4 years ago
- Category set to Packaging
- Assignee deleted (
Evgeni Golov)
Updated by Tomer Brisker almost 4 years ago
- Fixed in Releases 2.1.4, 2.2.0 added
- Fixed in Releases deleted (
2.3.0)
Actions