Bug 1861815

Summary: Error only on production builds: The Dynflow world was not initialized yet. If your plugin uses it, make sure to call Rails.application.dynflow.require! in some initializer
Product: Red Hat Satellite Reporter: Jeremy Lenz <jlenz>
Component: Subscription ManagementAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Cole Higgins <chiggins>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.8.0   
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-30 14:26:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jeremy Lenz 2020-07-29 16:01:24 UTC 
When running a rake task that includes the Katello::SubscriptionMailer, it fails with error:

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

Only seems to happen on nightly; not on devel boxes.

Steps to reproduce

# Import a manifest with at least one subscription that expires <180 days
# Attach that subscription to a host
# Run the Subscriptions - Entitlement Report (Monitor -> Report Templates) with Days from Now set appropriately
# Verify that the report shows that host and subscription
# In My Account -> Email Preferences, set up the Subscriptions Expiring Soon email and configure for Daily emails
# Run /usr/sbin/foreman-rake reports:daily

Expected: no output; if email is set up you are emailed the report
Actual: the error above

Alternate steps to reproduce (doesn't require a host/subscription)

In foreman-rake console, run

 include Katello::SubscriptionMailerHelper
 start_report_task(120)


Expected: return the job ID as a string
Actual: the error above

Workaround

See workaround in https://projects.theforeman.org/issues/29337#note-2
Comment 1 Jeremy Lenz 2020-07-29 16:01:27 UTC 
Created from redmine issue https://projects.theforeman.org/issues/30511
Comment 2 Brad Buckingham 2020-07-30 14:26:18 UTC 

*** This bug has been marked as a duplicate of bug 1861816 ***