Actions
Bug #28095
closedConcurrency control doesn't work when batch planning is enabled
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
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