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 2143515 - ERROR -- /parallel-executor-core: no manager for Dynflow::Director::Event for event: #<Actions::ProxyAction::ProxyActionStopped
Summary: ERROR -- /parallel-executor-core: no manager for Dynflow::Director::Event for...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.11.3
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.13.0
Assignee: Adam Ruzicka
QA Contact: Peter Ondrejka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-17 04:20 UTC by Hao Chang Yu
Modified: 2023-05-10 08:26 UTC (History)
2 users (show)

Fixed In Version: foreman-tasks-7.1.1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-03 13:23:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 35950 0 Normal Closed Delivery of ProxyActionStopped should be optional 2023-01-18 12:00:20 UTC
Github theforeman foreman-tasks pull 704 0 None open Fixes #35950 - Make delivery of ProxyActionStopped events optional 2023-01-16 10:31:44 UTC
Red Hat Issue Tracker SAT-14083 0 None None None 2022-11-29 00:35:58 UTC
Red Hat Product Errata RHSA-2023:2097 0 None None None 2023-05-03 13:23:18 UTC

Description Hao Chang Yu 2022-11-17 04:20:37 UTC 
Description of problem:
Getting the following errors in the /var/log/messages when running remote execution jobs.
--------------
dynflow-sidekiq@orchestrator: E, [2022-11-15T08:49:29.338032 #XXXXX] ERROR -- /parallel-executor-core: no manager for Dynflow::Director::Event[request_id: e7012c15-8eeb-4e5c-87cf-1a34799350d7-1577, execution_plan_id: 8e3869cc-909f-4218-8e25-822d29f1c003, step_id: 3, event: #<Actions::ProxyAction::ProxyActionStopped:0xXXXXXXXXX>, result: #<Concurrent::Promises::ResolvableFuture:0xXXXXXXXXX pending>, optional: false] (Dynflow::Error)

dynflow-sidekiq@orchestrator: E, [2022-11-15T08:49:29.336864 #XXXXX] ERROR -- /parallel-executor-core: no manager for Dynflow::Director::Event[request_id: e7012c15-8eeb-4e5c-87cf-1a34799350d7-1575, execution_plan_id: 553dffde-6c86-420f-a8ed-d26a2e0e12fa, step_id: 3, event: #<Actions::ProxyAction::ProxyActionStopped:0xXXXXXXXXX>, result: #<Concurrent::Promises::ResolvableFuture:0xXXXXXXXXX pending>, optional: false] (Dynflow::Error)

dynflow-sidekiq@orchestrator: E, [2022-11-15T08:49:16.902160 #XXXXX] ERROR -- /parallel-executor-core: no manager for Dynflow::Director::Event[request_id: e7012c15-8eeb-4e5c-87cf-1a34799350d7-1566, execution_plan_id: a9af512c-32a1-4c4d-8972-e9429a361eda, step_id: 3, event: #<Actions::ProxyAction::ProxyActionStopped:0xXXXXXXXXX>, result: #<Concurrent::Promises::ResolvableFuture:0xXXXXXXXXX pending>, optional: false] (Dynflow::Error)
--------------

This issue seems to be similar to bug #1939450.

This is what I understand

"CheckOnProxyActions" task is scheduled to check the status of the REX jobs every 10 minutes in case it does not receive the callback from clients. This task checks each REX job on client side and then send an event to notify Satellite that the REX job has been completed. The above error means the REX job is finished before the event is sent.


Example 1:
REX job received the first notification from "CheckOnProxyActions" task at "2022-11-15 13:46:07 UTC" ( as it took more than 20 minutes to run. It process the event (on_proxy_action_stopped hook) and raise error because the task failed on client side.
----------------------
dynflow_steps:
8e3869cc-909f-4218-8e25-822d29f1c003,3,2,,error,2022-11-15 13:22:00,2022-11-15 13:46:07.185677,1447.185677213,0.922984392,0.5,1,Dynflow::ExecutionPlan::Steps::RunStep,{"class":"Dynflow::ExecutionPlan::Steps::Error","exception_class":"Foreman::Exception","message":"ERF42-0142 [Foreman::Exception]: The capsule task 9e1d3200-6e10-42ee-93ad-cecdfbeb812e failed.","backtrace":["/opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-4.1.5/app/lib/actions/proxy_action.rb:90:in `check_task_status'","/opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-4.1.5/app/lib/actions/proxy_action.rb:137:in `on_proxy_action_stopped'","   <=======================
----------------------

Run host job stopped at "2022-11-15 13:49:28 UTC"
----------------------
1280c827-510e-425a-ade5-70e14c6af231 | ForemanTasks::Task::DynflowTask | Actions::RemoteExecution::RunHostJob                 | 2022-11-15 12:24:26.703 | 2022-11-15 13:49:28.785 | stopped   | error     | 8e3869cc-909f-4218-8e25-822d29f1c003 | 3d342956-b7a4-4510-8a22-e8a9be7118d8 | 2022-11-15 12:24:12.914109 |              | Remote action: XXXXXXX
----------------------

Another notification send to the same REX Job at "Nov 15 08:49:29"  (UTC +00). The REX job has received the first notification about 3 minutes ago and stopped so Dynflow raise the error.
----------------------
/var/log/messages:
dynflow-sidekiq@orchestrator: E, [2022-11-15T08:49:29.338032 #XXXXX] ERROR -- /parallel-executor-core: no manager for Dynflow::Director::Event[request_id: e7012c15-8eeb-4e5c-87cf-1a34799350d7-1577, execution_plan_id: 8e3869cc-909f-4218-8e25-822d29f1c003, step_id: 3, event: #<Actions::ProxyAction::ProxyActionStopped:0xXXXXXXXXX, result: #<Concurrent::Promises::ResolvableFuture:0xXXXXXXXXX pending>, optional: false] (Dynflow::Error)
----------------------


Example 2:
The run host job was finished successfully at "2022-11-15 13:49:08"
----------------------
a9af512c-32a1-4c4d-8972-e9429a361eda,1,1,,success,2022-11-15 12:17:17.981888,2022-11-15 12:22:49.476562,331.494674682,331.494674682,1,0,Dynflow::ExecutionPlan::Steps::PlanStep,,Actions::RemoteExecution::RunHostJob,[2],
a9af512c-32a1-4c4d-8972-e9429a361eda,3,2,,success,2022-11-15 13:21:00,2022-11-15 13:46:06.52477,1506.52477077,0.373142927,1,1,Dynflow::ExecutionPlan::Steps::RunStep,,Actions::ProxyAction,,remote_execution
a9af512c-32a1-4c4d-8972-e9429a361eda,4,1,,success,2022-11-15 13:49:08.117074,2022-11-15 13:49:08.405157,0.288083601,0.288083601,1,1,Dynflow::ExecutionPlan::Steps::FinalizeStep,,Actions::RemoteExecution::RunHostJob,,remote_execution
----------------------

An event was sent at "2022-11-15T08:49:16 UTC -05:00" raise error because the task was finished.
----------------------
dynflow-sidekiq@orchestrator: E, [2022-11-15T08:49:16.902160 #XXXXXX] ERROR -- /parallel-executor-core: no manager for Dynflow::Director::Event[request_id: e7012c15-8eeb-4e5c-87cf-1a34799350d7-1566, execution_plan_id: a9af512c-32a1-4c4d-8972-e9429a361eda, step_id: 3, event: #<Actions::ProxyAction::ProxyActionStopped:0xXXXXXXXXX>, result: #<Concurrent::Promises::ResolvableFuture:0xXXXXXXXXX pending>, optional: false] (Dynflow::Error)
----------------------
Comment 3 Peter Ondrejka 2023-01-30 12:22:04 UTC 
Verified on Satellite 6.13 snap 7, using a job run with command "sleep 550" against a number of hosts, the aforementioned error is no longer logged
Comment 6 errata-xmlrpc 2023-05-03 13:23:05 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.13 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-2023:2097
Note You need to log in before you can comment on or make changes to this bug.