Project

General

Profile

Actions
Copy link

Bug #18206

closed

Upgrade raises "No executor available (Dynflow::Error)" at db:seed step

Added by Martin Bacovsky almost 8 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Martin Bacovsky
Category:
-
Target version:
1.11.1
Difficulty:
Triaged:
Bugzilla link:
1413966
Pull request:
https://github.com/Dynflow/dynflow/pull/213
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1413966

Description of problem:
Performed upgrade from sat6.2 -> 6.2.7 on rhel7 aw/ customer db. Upgrade was completed but I see errors on console at db_seed step :

--
Upgrade Step: db_seed...

[Sat_SERVER] out: E, [2017-01-13T06:20:01.007010 #16653] ERROR -- /connector-database-core: No executor available (Dynflow::Error)

[Sat_SERVER] out: E, [2017-01-13T06:20:01.007245 #16653] ERROR -- /client-dispatcher: No executor available (Dynflow::Error)
--

[Sat_SERVER] out: E, [2017-01-13T06:20:01.007010 #16653] ERROR -- /connector-database-core: No executor available (Dynflow::Error)
[Sat_SERVER] out: /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.13.3/lib/dynflow/connectors/database.rb:142:in `any_executor'
[Sat_SERVER] out: /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.13.3/lib/dynflow/connectors/database.rb:134:in `find_receiver'
[Sat_SERVER] out: /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.13.3/lib/dynflow/connectors/database.rb:86:in `handle_envelope'
[Sat_SERVER] out: /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.13.3/lib/dynflow/actor.rb:6:in `on_message'
[Sat_SERVER] out: /opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/context.rb:46:in `on_envelope'
[Sat_SERVER] out: /opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/executes_context.rb:7:in `on_envelope'

[Sat_SERVER] out: E, [2017-01-13T06:20:01.007245 #16653] ERROR -- /client-dispatcher: No executor available (Dynflow::Error)
[Sat_SERVER] out: /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.13.3/lib/dynflow/connectors/database.rb:142:in `any_executor'
[Sat_SERVER] out: /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.13.3/lib/dynflow/connectors/database.rb:134:in `find_receiver'
[Sat_SERVER] out: /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.13.3/lib/dynflow/connectors/database.rb:86:in `handle_envelope'
[Sat_SERVER] out: /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.13.3/lib/dynflow/actor.rb:6:in `on_message'
[Sat_SERVER] out: /opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/context.rb:46:in `on_envelope'
[Sat_SERVER] out: /opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/executes_context.rb:7:in `on_envelope'

Version-Release number of selected component (if applicable):
upgrade sat6.2 to 6.2.7

How reproducible:
once w/ customer db

Actual results:
Upgrade was completed however, got reported errors under "upgrade: db seed" step

Expected results:
no errors should be raised while performing upgrade

Additional info:
The behaviour can be seen when the DB contains tasks in running state and no executor is running.
During db:seed the Dynflow that is being initiated is trying to recover and is trying to restart the tasks. When no executor is running the error is risen. It is not harmful because the task will be resumed on next executor start, but the error should not be displayed.

Actions
Copy link

Also available in: Atom PDF