Remote execution with Concurrency 1 very slow after update Foreman to 1.24

When yo run an ansible/ssh job template changing concurrency to 1 the execution is very slow. The job output shows the result but not change to the next host until aprox 10 minutes.
I’m using for this tests the predefined ssh command template to execute only “uname -a”.

I’ve update yesterday to fix other issues on remote execution. Some version packages:

foreman-1.24.0-15.el7.noarch
foreman-cli-1.24.0-15.el7.noarch
foreman-debug-1.24.0-15.el7.noarch
foreman-installer-1.24.0-7.el7.noarch
foreman-installer-katello-1.24.0-7.el7.noarch
foreman-postgresql-1.24.0-15.el7.noarch
foreman-proxy-1.24.0-5.el7.noarch
foreman-release-1.24.0-4.el7.noarch
foreman-release-scl-7-2.el7.noarch
foreman-selinux-1.24.0-4.el7.noarch
foreman-vmware-1.24.0-15.el7.noarch
rubygem-foreman_maintain-0.5.0-1.el7.noarch
rubygem-foreman_maintain-doc-0.5.0-1.el7.noarch
tfm-rubygem-foreman_ansible-4.0.3-1.fm1_24.el7.noarch
tfm-rubygem-foreman_ansible_core-3.0.1-1.fm1_24.el7.noarch
tfm-rubygem-foreman_ansible_core-3.0.2-1.fm1_25.el7.noarch
tfm-rubygem-foreman_ansible_core-doc-3.0.1-1.fm1_24.el7.noarch
tfm-rubygem-foreman_ansible-doc-4.0.3-1.fm1_24.el7.noarch
tfm-rubygem-foreman_remote_execution-2.0.6-1.fm1_24.el7.noarch
tfm-rubygem-foreman_remote_execution_core-1.3.0-1.el7.noarch
tfm-rubygem-foreman_remote_execution_core-doc-1.3.0-1.el7.noarch
tfm-rubygem-foreman_remote_execution-doc-2.0.6-1.fm1_24.el7.noarch
tfm-rubygem-foreman_scc_manager-1.7.0-2.fm1_24.el7.noarch
tfm-rubygem-foreman_scc_manager-doc-1.7.0-2.fm1_24.el7.noarch
tfm-rubygem-foreman-tasks-0.17.5-1.fm1_24.el7.noarch
tfm-rubygem-foreman-tasks-core-0.3.3-1.fm1_24.el7.noarch
tfm-rubygem-foreman-tasks-core-doc-0.3.3-1.fm1_24.el7.noarch
tfm-rubygem-foreman-tasks-doc-0.17.5-1.fm1_24.el7.noarch
tfm-rubygem-foreman_templates-7.0.5-1.fm1_24.el7.noarch
tfm-rubygem-foreman_templates-doc-7.0.5-1.fm1_24.el7.noarch

Thank you!

Bug open:
https://projects.theforeman.org/issues/28095

WA works ok.

Merged with another issue at:

I mentioned this behavior right now with

Version 2.2.2 © 2009-2021 …

Can somebody confirm this?