Bug 1943347

Description of problem:

A group of hosts was selected, and an ansible roles run was initiated from Satellite.  1 of the hosts has an issue which displays a DEPRECATION WARNING for one of the tasks.  This warning appears in every job tasks for all of the hosts, not just for the host that has the issue.  When the ansible roles are ran against individual hosts (1 at a time), the DEPRECATION WARNING does not display for any of the hosts (except for the one having issues).


An example where the error is on host2, however, the playbook is ran against host1:

~~~
TASK [Gathering Facts]**********************************************************
ok: [host1]
[DEPRECATION WARNING]: Distribution redhat 8.3 on host host2 should use /usr/libexec/platform-python, but is using
/usr/bin/python for backward compatibility with prior Ansible releases. A future Ansible release will default to using the
discovered platform python for this host. See
https://docs.ansible.com/ansible/2.9/reference_appendices/interpreter_discovery.html for more information. This feature will
be removed in version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
~~~


Version-Release number of selected component (if applicable):
Satellite 6.8

How reproducible:
always

Steps to Reproduce:
1. Select a number of hosts to run ansible roles on (make sure one of the hosts will throw the DEPRECATION WARNING message)
2. Review the tasks for any of the individual hosts, and you will see the same unrelated host appearing in the DEPRECATION WARNING
3.

Actual results:
DEPRECATION WARNING message for 1 particular host appears in the job tasks for all hosts that ran in the same group

Expected results:
expect the DEPRECATION WARNING message to only be displayed for the task of the host the warning is for

Additional info: