Actions
Bug #30919
closedsync_task fails with `The Dynflow world was not initialized yet.` in rake tasks on nightly production
Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Orchestration
Target version:
-
Description
Cloning from the earlier issue where this was added to other rake tasks using Dynflow tasks. This issue is specifically for the katello:pulp3_post_migration_check as reported in community post :
https://community.theforeman.org/t/contentmigration-run-content-switchover-failed/20476
foreman-maintain advanced procedure run content-switchover failed with : Performing a check to verify everything that is needed has been migrated [FAIL] Failed executing foreman-rake katello:pulp3_post_migration_check, exit status 1: rake aborted! The Dynflow world was not initialized yet. If your plugin uses it, make sure to call Rails.application.dynflow.require! in some initializer
Updated by Samir Jha about 4 years ago
- Copied from Bug #29337: async_task fails with `The Dynflow world was not initialized yet.` in rake tasks on nightly production added
Updated by John Mitsch about 4 years ago
- Is duplicate of Bug #30937: katello:pulp3_post_migration_check fails with 'The Dynflow world was not initialized yet' added
Updated by John Mitsch about 4 years ago
- Status changed from New to Duplicate
- Triaged changed from No to Yes
Actions