Project

General

Profile

Actions

Bug #29235

closed

When setting foreman_tasks_proxy_batch_trigger to false ansible jobs configured in foreman do not work anymore

Added by Dominik Matoulek over 5 years ago. Updated over 5 years ago.

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

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1785250

When setting foreman_tasks_proxy_batch_trigger to false, ansible jobs do not work anymore in foreman.

I'm currently not aware why setting batch triggering to false should prevent ansible from functioning. Someone would have to look into that.

Description of problem:
When setting foreman_tasks_proxy_batch_trigger to false ansible jobs configured in foreman do not work anymore

How reproducible:
always

Steps to Reproduce:
1. Create a job on 3 hosts (use ansible template)
2. Run the job with foreman_tasks_proxy_batch_trigger to false
3. Observe the times of jobs being not executed.

Actual results:
should run them in parallel at least

Expected results:
I would expect that if Foreman is able to run all 3 jobs at once in short time.

Actions #1

Updated by Dominik Matoulek over 5 years ago

  • Subject changed from When setting foreman_tasks_proxy_batch_trigger to false ansible jobs configured in satellite do not work anymore to When setting foreman_tasks_proxy_batch_trigger to false ansible jobs configured in foreman do not work anymore
  • Description updated (diff)
Actions #2

Updated by Dominik Matoulek over 5 years ago

  • Triaged changed from No to Yes
Actions #3

Updated by Dominik Matoulek over 5 years ago

  • Status changed from New to Duplicate
Actions

Also available in: Atom PDF