Well, the controller I'm running the playbook from is RHEL 8 and has the following version:
ansible [core 2.14.6]
config file = /etc/ansible/ansible.cfg
configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python3.9/site-packages/ansible
ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
executable location = /bin/ansible
python version = 3.9.16 (main, May 31 2023, 12:21:58) [GCC 8.5.0 20210514 (Red Hat 8.5.0-18)] (/usr/bin/python3.9)
jinja version = 3.1.2
libyaml = True
I tweaked the playbook to only try to run to one host, and the -vvv does show this:
<server1> (127, b'/bin/sh: /usr/bin/python3: No such file or directory\r\n'
server1 is the RHEL 7 target, and /etc/ansible/hosts doesn't specify the ansible_interpreter. I have "ansible_interpreter=/usr/bin/python3" on our RHEL 8 boxes in /etc/ansible/hosts. So do I need to specify something specific for python 2.7.5 on those RHEL 7 hosts?
Thanks,
Harry