Project

General

Profile

Actions

Bug #16666

closed

Auto-execute run in db:seed

Added by Ivan Necas over 7 years ago. Updated over 5 years ago.

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

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


Related issues 1 (0 open1 closed)

Related to foreman-tasks - Bug #16668: Dont crash when other executor is auto-executingClosedIvan Necas09/23/2016Actions
Actions #1

Updated by Ivan Necas over 7 years ago

  • Related to Bug #16668: Dont crash when other executor is auto-executing added
Actions #2

Updated by Ivan Necas over 7 years ago

  • Bugzilla link set to 1378913
Actions #3

Updated by The Foreman Bot over 7 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/foreman-tasks/pull/203 added
Actions #4

Updated by Ivan Necas over 7 years ago

  • Target version changed from 127 to 1.5.1
Actions #5

Updated by Ivan Necas over 7 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF