Actions
Bug #16666
closedAuto-execute run in db:seed
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Description
The auto-execute feature is meant to be run once the permanent
executor is starting to pick up tasks that were queed while no
executor was avaiable. However, we run executor also in db:seed (to
not be dependent on external executor at this phase). This can lead to
auto-execute to be run there as well, with errors like this:
Sequel::UniqueConstraintViolation: PG::Error: ERROR: duplicate key value
violates unique constraint "dynflow_coordinator_records_pkey"
DETAIL: Key (id, class)=(auto-execute,
Dynflow::Coordinator::AutoExecuteLock) already exists.
The solution should be not trying to auto-execute inside rake tasks
Updated by Ivan Necas about 8 years ago
- Related to Bug #16668: Dont crash when other executor is auto-executing added
Updated by The Foreman Bot about 8 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman-tasks/pull/203 added
Updated by Ivan Necas about 8 years ago
- Target version changed from 127 to 1.5.1
Updated by Ivan Necas about 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset ab2f22d6cdb6adf96448365aec2324eee32f0f77.
Actions