Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1861816

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: Justin Sherrill <jsherril>
Status: CLOSED ERRATA QA Contact: Cole Higgins <chiggins>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.8.0CC: ehelms, pcreech
Target Milestone: 6.8.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-katello-3.16-1.rc1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 13:04:48 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:04:11 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:04:14 UTC
Created from redmine issue https://projects.theforeman.org/issues/30511

Comment 2 Jeremy Lenz 2020-07-29 16:04:16 UTC
Upstream bug assigned to None

Comment 3 Brad Buckingham 2020-07-30 14:26:18 UTC
*** Bug 1861815 has been marked as a duplicate of this bug. ***

Comment 4 Bryan Kearney 2020-07-30 20:01:43 UTC
Upstream bug assigned to jsherril

Comment 5 Bryan Kearney 2020-07-30 20:01:45 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30511 has been resolved.

Comment 10 errata-xmlrpc 2020-10-27 13:04:48 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.8 release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:4366