+++ This bug was initially created as a clone of Bug #1962847 +++

+++ This bug was initially created as a clone of Bug #1959901 +++

Description of problem:

While running any foreman-rake command under Katello namespace fails with below error message.

{:status=>"FAIL", :message=>
      "The Dynflow world was not initialized yet. If your plugin uses it, make sure to call Rails.application.dynflow.require! in some initializer"},

Eg:
# foreman-rake katello:check_ping
{:services=>
  {:candlepin=>{:status=>"ok", :duration_ms=>"29"},
   :candlepin_auth=>{:status=>"ok", :duration_ms=>"27"},
   :foreman_tasks=>
    {:status=>"FAIL",
     :message=>
      "The Dynflow world was not initialized yet. If your plugin uses it, make sure to call Rails.application.dynflow.require! in some initializer"},
   :katello_events=>
    {:status=>"ok", :message=>"38 Processed, 0 Failed", :duration_ms=>"0"},
   :candlepin_events=>
    {:status=>"ok", :message=>"71 Processed, 0 Failed", :duration_ms=>"0"},
   :pulp=>{:status=>"ok", :duration_ms=>"82"},
   :pulp_auth=>{:status=>"ok", :duration_ms=>"40"}},
 :status=>"FAIL"}
rake aborted!
Not all the services have been started. Check the status report above and try again.
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.18.1.22/lib/katello/tasks/reimport.rake:10:in `block (2 levels) in <top (required)>'
/opt/rh/rh-ruby25/root/usr/share/gems/gems/rake-12.3.0/exe/rake:27:in `<top (required)>'
Tasks: TOP => katello:check_ping
(See full trace by running task with --trace)



Version-Release number of selected component (if applicable):
6.9

How reproducible:

Always
Steps to Reproduce:
1. execute any foreman-rake command with katello namespace.
2.
3.

Actual results:

The Dynflow world was not initialized yet. If your plugin uses it, make sure to call Rails.application.dynflow.require! in some initializer


Expected results:

This should work without error
Additional info:

--- Additional comment from  on 2021-05-12T15:04:30Z 

*** Bug 1959888 has been marked as a duplicate of this bug. ***

--- Additional comment from  on 2021-05-12T15:05:45Z 

*** Bug 1959878 has been marked as a duplicate of this bug. ***