Project

General

Profile

Actions
Copy link

Bug #28095

closed

Concurrency control doesn't work when batch planning is enabled

Added by Adam Ruzicka about 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Adam Ruzicka
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
1781671
Pull request:
https://github.com/theforeman/foreman-tasks/pull/489
Fixed in Releases:
foreman-tasks-1.1.0
Found in Releases:
Red Hat JIRA:

Description

Reproducible: Always

Steps to reproduce:
1) Create a REX job, set time span on concurrency level to some value

Expected results:
Job runs are spanning the given timeframe (if time span is set) or at most $CONCURRENCY_LEVEL jobs are running at once

Actual results:
Depending on the settings, jobs can either run all at once or get stuck

Workaround:
Go to Settings > Foreman Tasks > set 'foreman_tasks_proxy_batch_trigger' to false. Please note this can lead to degraded performance in case you have lots of hosts.

Actions
Copy link
 #1

Updated by Adam Ruzicka about 5 years ago

  • Bugzilla link set to 1781671
Actions
Copy link
 #2

Updated by The Foreman Bot almost 5 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Adam Ruzicka
  • Pull request https://github.com/theforeman/foreman-tasks/pull/489 added
Actions
Copy link
 #3

Updated by The Foreman Bot almost 5 years ago

  • Fixed in Releases foreman-tasks-1.0.2 added
Actions
Copy link
 #4

Updated by Anonymous almost 5 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link
 #5

Updated by Adam Ruzicka over 4 years ago

  • Fixed in Releases foreman-tasks-1.1.0 added
  • Fixed in Releases deleted (foreman-tasks-1.0.2)
Actions
Copy link

Also available in: Atom PDF