Project

General

Profile

Actions

Bug #20908

closed

Postpone the initialization of dynflow

Added by Ivan Necas about 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

In #18618, the initialization code was moved from foreman-tasks to foreman. There was however one
thing done differently, where the initialization of dynflow world was moved directly to the
time `Rails.application.dynflow` was called. This is not right, as there are situations where
plugins go and call `Rails.application.dynflow.config` before the whole stack is prepared, which leads to
database connection being opened too early, which can cause the whole lot of issues (as we've hit currently with Katello).

After we released #18673, the Katello tests started failing on

ActiveRecord::StatementInvalid: PG::ObjectInUse: ERROR:  database "test_develop_pr_katello-2-test" is being accessed by other users
DETAIL:  There are 3 other sessions using the database.

That was due to fact that the dynflow world was initialized too early.


Related issues 2 (0 open2 closed)

Related to Foreman - Feature #18618: Use Dynflow as an ActiveJob backendClosedDaniel Lobato Garcia02/22/2017Actions
Related to foreman-tasks - Bug #18673: Remove initialization code in favor of DynflowClosedDaniel Lobato Garcia02/24/2017Actions
Actions #1

Updated by Ivan Necas about 6 years ago

  • translation missing: en.field_release set to 240

We should handle this before 1.16 gets out

Actions #2

Updated by Ivan Necas about 6 years ago

  • Related to Feature #18618: Use Dynflow as an ActiveJob backend added
Actions #3

Updated by Ivan Necas about 6 years ago

  • Related to Bug #18673: Remove initialization code in favor of Dynflow added
Actions #4

Updated by The Foreman Bot about 6 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/4826 added
Actions #5

Updated by Ivan Necas about 6 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF