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 1962840

Summary:	dynflow_executor.output grows extremely large in short period of time.
Product:	Red Hat Satellite	Reporter:	James Jeffers <jjeffers>
Component:	Dynflow	Assignee:	Adam Ruzicka <aruzicka>
Status:	CLOSED ERRATA	QA Contact:	Lukáš Hellebrandt <lhellebr>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.7.0	CC:	aganbat, ahumbe, arahaman, aruzicka, dhjoshi, dmule, dsynk, egolov, gopinath.perumal, gscarbor, jbhatia, jjeffers, ktordeur, sadas, saydas, sbeal, sboyron
Target Milestone:	6.10.0	Keywords:	PrioBumpGSS, Triaged
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	tfm-rubygem-dynflow-1.4.8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1877917	Environment:
Last Closed:	2021-11-16 14:11:01 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:

Comment 4 Lukáš Hellebrandt 2021-06-30 13:00:57 UTC

Verified with Sat 6.10.0 snap 5.0.

Used reproducer (don't forget to change the TASKS_ROOT to current foreman-tasks version): https://gist.github.com/adamruzicka/3a4681f488e5978c7bd49e544f1ce124 (thanks Adam). Without switching to the old dynflow, the bug is not reproducible since sidekiq-based dynflow never had this issue.

In 6.8, upon invoking the reproducer, there were 5816 lines added to the production.log (basically an absurdly long traceback). In 6.10.0, it's only 59 lines (a shorter and perhaps more useful traceback). No regression was found (manually, automation results not available) => VERIFIED.

Comment 8 errata-xmlrpc 2021-11-16 14:11:01 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 (Moderate: Satellite 6.10 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-2021:4702