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 1939454 - ERROR -- /parallel-executor-core: no manager for Dynflow::Director::Event
Summary: ERROR -- /parallel-executor-core: no manager for Dynflow::Director::Event
Keywords:
Status: CLOSED DUPLICATE of bug 1939450
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Dynflow
Version: 6.8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-16 12:36 UTC by Michael Vollmer
Modified: 2021-03-17 09:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-17 09:31:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.