Ansible jobtemplates exists abnormally in the middle without RECAP. Foreman says status OK

Support
1

Problem: Ansible job template exits in the middle of the play with status 0 or 2 and without recap:
…
“Complete!”,
“Uploading Enabled Repositories Report”,
“Loaded plugins: fastestmirror, product-id, subscription-manager”,
“Loaded plugins: fastestmirror, product-id, subscription-manager”,
“Loaded plugins: fastestmirror, product-id, subscription-manager”,
“Loaded plugins: fastestmirror, product-id, subscription-manager”,
“Loaded plugins: fastestmirror, product-id, subscription-manager”
]
]
}

Expected outcome:

Foreman and Proxy versions:

Foreman and Proxy plugin versions:

Distribution and version:

Other relevant data:

2

Sorry, now the complete message:

Problem: Ansible job template exits abruptly in the middle of the play with status 0 or 2 and without RECAP.
The task where the job finish can be executed ok or not but the finish its the same. Exits abruptly in the middle of the play (not execute next tasks) and Foreman job template says ok at job invocation page.

After some tests, I see the problem is always with debug module and the output generated to stdout. Seems like some character at this stdout generate the problem. Removing debug module (comment) remove the problem. Perphaps some problem at callback pluging?

Example of output:

…
“Complete!”,
“Uploading Enabled Repositories Report”,
“Loaded plugins: fastestmirror, product-id, subscription-manager”,
“Loaded plugins: fastestmirror, product-id, subscription-manager”,
“Loaded plugins: fastestmirror, product-id, subscription-manager”,
“Loaded plugins: fastestmirror, product-id, subscription-manager”,
“Loaded plugins: fastestmirror, product-id, subscription-manager”
]
]
}
status 0

The problem appears with others stdout (and allways with they) but not with all stoduts. So I suspect some character at the conflicting stdouts.

Expected outcome: Foreman says KO, job template shows RECAP if the task goes wrong. Foreman says OK, job template continue if the task goes right.

Foreman and Proxy versions: 1.24.2

3

The problem seems appears when you print (debug module) a long output from a stdout registered output, perhaps about 1200 lines.