Bug #29258
Dynflow world gets shared across puma workers in production
Pull request:
Found in Releases:
Associated revisions
Refs #29258 - Lazy initialize dynflow during rake tasks
which need executor
History
#1
Updated by The Foreman Bot 12 months ago
Updated by - Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/7487 added
#2
Updated by The Foreman Bot 12 months ago
- Fixed in Releases 2.1.0 added
#3
Updated by Adam Ruzicka 12 months ago
Updated by - Status changed from Ready For Testing to Closed
Applied in changeset 29fe60a89b47dfb4292f7a4d28d5eb6f5576b488.
#4
Updated by The Foreman Bot 12 months ago
- Pull request https://github.com/theforeman/foreman/pull/7490 added
#5
Updated by The Foreman Bot 10 months ago
- Pull request https://github.com/theforeman/foreman/pull/7614 added
#6
Updated by The Foreman Bot 10 months ago
- Pull request https://github.com/theforeman/foreman/pull/7615 added
#7
Updated by Tomer Brisker 10 months ago
Updated by - Category set to Plugin integration
- Fixed in Releases 1.24.3, 2.0.1 added
Fixes #29258 - Initialize dynflow in puma workers
When running puma in clustered mode in production, Dynflow would get initialized
in the master process before workers were forked off and due to CoW the workers
would use the same world id.
With this commit we will eagerly initialize Dynflow only when running under
Passenger. When running under puma, we will initialize Dynflow in workers.
Co-Authored-By: Ewoud Kohl van Wijngaarden <ewoud@kohlvanwijngaarden.nl>