Project

General

Profile

Actions

Bug #12088

closed

When executor with a role of delayed executor exits in a non-standard way, new executor would take over the job

Added by Ivan Necas about 9 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

The problem is, when a Dynflow executor exits in non-standard way, a lock that prevents other executors
to take over the delayed execution is not released.

A workaround is to run this in rails console:

coordinator = ForemanTasks.dynflow.world.coordinator
coordinator.find_locks(class: Dynflow::Coordinator::DelayedExecutorLock.name).each { |l| coordinator.release(l) }

and then restart the executor. After doing so, the one should see a flag "delayed_executor"=>true in dynflow console /foreman_tasks/dynflow/worlds at some executor world.

Actions #1

Updated by Ivan Necas about 9 years ago

  • Status changed from Assigned to Ready For Testing

The fix should be on dynflow side, to make sure the locks are released properly https://github.com/Dynflow/dynflow/pull/171

Actions #2

Updated by Marek Hulán about 9 years ago

  • Status changed from Ready For Testing to Assigned
  • Translation missing: en.field_release set to 99

The fix for this should bump the dynflow dependency I think

Actions #3

Updated by Ivan Necas about 9 years ago

  • Project changed from Foreman Remote Execution to foreman-tasks
Actions #4

Updated by Ivan Necas about 9 years ago

  • Status changed from Assigned to Closed
  • Translation missing: en.field_release changed from 99 to 100
Actions

Also available in: Atom PDF