Project

General

Profile

Actions
Copy link

Bug #21361

open

when satellite is starting, there are 4 of "RuntimeError: The Dynflow world was not initialized yet. If your plugin uses it, make sure to call ForemanTasks.dynflow.require! in some initializer" in production.log

Added by Adam Ruzicka over 6 years ago. Updated almost 6 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
1501949
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1501949

Description of problem:
when satellite is starting, there are four of "RuntimeError: The Dynflow world was not initialized yet. If your plugin uses it, make sure to call ForemanTasks.dynflow.require! in some initializer" in production.log

Version-Release number of selected component (if applicable):
satellite-6.3.0-19.0.beta.el7sat.noarch
tfm-rubygem-foreman-tasks-0.9.6-1.fm1_15.el7sat.noarch

How reproducible:
always

Steps to Reproduce:
1. Restart system with Satellite and watch production.log while Satellite
is starting

Actual results:
See tracebacks in attached log

Expected results:
There should be no tracebacks

Additional info:
Usually tracebacks during start if everything works after that seems harmless, but this one sugests there might be a way how to suppress it: "make sure to call ForemanTasks.dynflow.require! in some initializer"

Actions
Copy link

Also available in: Atom PDF