Feature #29282
Add migrations for replacing passenger with puma
Pull request:
Fixed in Releases:
Found in Releases:
Description
At this point, puma is default in nightly. This issue is to track the migrations required for enabling puma on upgrades.
Related issues
Associated revisions
Fixes #29282 - Enable Puma migration on compatible upgrades
The commit bd02fbd reverted commit 0b244f5.
https://github.com/theforeman/puppet-foreman/pull/814 fixed the race
condition of systemctl start foreman returning immediately before the
service was up.
History
#1
Updated by Suresh Thirugnanasambandan over 2 years ago
Updated by - Tracker changed from Bug to Feature
#2
Updated by Suresh Thirugnanasambandan over 2 years ago
- Blocks Tracker #28999: Deploy Foreman with Puma as the application server by default added
#3
Updated by Suresh Thirugnanasambandan over 2 years ago
- Blocks deleted (Tracker #28999: Deploy Foreman with Puma as the application server by default)
#4
Updated by Suresh Thirugnanasambandan over 2 years ago
- Related to Tracker #28999: Deploy Foreman with Puma as the application server by default added
#5
Updated by The Foreman Bot over 2 years ago
Updated by - Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman-installer/pull/484 added
#6
Updated by The Foreman Bot over 2 years ago
- Fixed in Releases 2.1.0 added
#7
Updated by Suresh Thirugnanasambandan over 2 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset installer|0b244f5623889585eb2b1a16a20ef659ebd2195f.
#8
Updated by The Foreman Bot over 2 years ago
- Pull request https://github.com/theforeman/foreman-installer/pull/495 added
Fixes #29282: Add migration to enable Puma