Bug 1939454

Summary: ERROR -- /parallel-executor-core: no manager for Dynflow::Director::Event
Product: Red Hat Satellite Reporter: Michael Vollmer <mivollme>
Component: DynflowAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.8.0CC: aruzicka
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: 2021-03-17 09:31:03 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 Michael Vollmer 2021-03-16 12:36:06 UTC 
Description of problem:
After any REX operation there is an error logged to /var/log/messages. This error is dumped even the REX operation completed successfully.

The delay between the start of the REX and the error message is exactly 10mins.

Version-Release number of selected component (if applicable):
Satellite Version: 6.8.4
tfm-rubygem-smart_proxy_dynflow-0.2.4-5.el7sat.noarch
foreman-dynflow-sidekiq-2.1.2.25-1.el7sat.noarch
tfm-rubygem-smart_proxy_dynflow_core-0.2.6-1.fm2_1.el7sat.noarch
tfm-rubygem-dynflow-1.4.7-1.fm2_1.el7sat.noarch

How reproducible:
any time after a rex operation

Steps to Reproduce:
1. Run hosts job: Run Ansible roles against hosts
2. wait 10mins
3. check the log

Actual results:
Mar 16 12:25:06 satellite dynflow-sidekiq@orchestrator: E, [2021-03-16T12:25:06.906185 #70350] ERROR -- /parallel-executor-core: no manager for Dynflow::Director::Event[request_id: 74481eab-f494-4bbb-8284-603189aca499-14, execution_plan_id: 638db861-064c-4988-aa38-09879c779f0d, step_id: 2, event: A
ctions::Middleware::WatchDelegatedProxySubTasks::CheckOnProxyActions, result: #<Concurrent::Promises::ResolvableFuture:0x000000001fadeea8 pending>] (Dynflow::Error)
Mar 16 12:25:06 satellite dynflow-sidekiq@orchestrator: /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-1.4.7/lib/dynflow/director.rb:167:in `handle_event'
Mar 16 12:25:06 satellite dynflow-sidekiq@orchestrator: /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-1.4.7/lib/dynflow/executors/abstract/core.rb:35:in `handle_event'
Mar 16 12:25:06 satellite dynflow-sidekiq@orchestrator: [ concurrent-ruby ]
Mar 16 12:25:06 satellite dynflow-sidekiq@orchestrator: /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-1.4.7/lib/dynflow/executors/abstract/core.rb:113:in `on_message'
Mar 16 12:25:06 satellite dynflow-sidekiq@orchestrator: [ concurrent-ruby ]
Mar 16 12:25:06 satellite dynflow-sidekiq@orchestrator: /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-1.4.7/lib/dynflow/executors/parallel.rb:42:in `delayed_event'
Mar 16 12:25:06 satellite dynflow-sidekiq@orchestrator: /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-1.4.7/lib/dynflow/clock.rb:36:in `apply'
Mar 16 12:25:06 satellite dynflow-sidekiq@orchestrator: /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-1.4.7/lib/dynflow/clock.rb:75:in `run_ready_timers'
Mar 16 12:25:06 satellite dynflow-sidekiq@orchestrator: /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-1.4.7/lib/dynflow/clock.rb:57:in `tick'
Mar 16 12:25:06 satellite dynflow-sidekiq@orchestrator: [ concurrent-ruby ]
Mar 16 12:25:06 satellite dynflow-sidekiq@orchestrator: /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-1.4.7/lib/dynflow/clock.rb:96:in `block in sleep_to'
Mar 16 12:25:06 satellite dynflow-sidekiq@orchestrator: [ concurrent-ruby ]

Expected results:
no error in the logs

Additional info:
Comment 1 Michael Vollmer 2021-03-17 09:31:03 UTC 

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