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 1849869

Summary: Unable to recycle the dynflow executor
Product: Red Hat Satellite Reporter: Hao Chang Yu <hyu>
Component: Tasks PluginAssignee: Adam Ruzicka <aruzicka>
Status: CLOSED ERRATA QA Contact: Peter Ondrejka <pondrejk>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.7.0CC: arahaman, aruzicka, pcreech, sadas, saydas
Target Milestone: 6.8.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-dynflow-1.4.6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-10-27 13:03:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Hao Chang Yu 2020-06-23 04:19:56 UTC
Description of problem:
Unable to recycle executor when the memory limit is reached. The world got terminated but no new world is created. The executor process doesn't exit.

Steps to Reproduce:
Setting the "EXECUTOR_MEMORY_LIMIT" to something very low which will trigger the refresh pretty much 60 seconds after the starting the executor.

----------------------------
#Set memory limit for executor process, before it's restarted automatically
EXECUTOR_MEMORY_LIMIT=200mb

#Set delay before first memory polling to let executor initialize (in sec)
EXECUTOR_MEMORY_MONITOR_DELAY=60 #default: 2 hours
----------------------------


Observed that:
- the world got terminated when the memory limit is reached.
- memory is not freed and no more executor showing in the Dynflow status page.
- running task will enter paused stated and never able to resume/cancel even after restarting the dynflowd.

Log:
Everything ready for world: da8f1461-7891-47a1-a39a-2ff44c0492bd
World has been terminated
<getting dead letter error>

# ps -aux | grep -i dynflow
foreman  18794 22.8  2.0 2572916 409472 ?      Sl   17:37   1:05 dynflow_executor
foreman  18795  0.0  0.6 581248 126556 ?       Sl   17:37   0:00 dynflow_executor_monitor

Same behaviour on both Satellite 6.6 and 6.7 but working on Satellite 6.5. 


Actual results:
failed to recycle executor

Expected results:
executor can be recycled successfully

Comment 2 Bryan Kearney 2020-06-23 08:05:47 UTC
Upstream bug assigned to aruzicka

Comment 3 Peter Ondrejka 2020-07-14 11:48:50 UTC
Verified on Satellite 6.8 snap 8

Comment 6 errata-xmlrpc 2020-10-27 13:03:32 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