This bug was initially created as a copy of Bug #1698176, that tracked adding a new setting so users could chose between ansible-runner and ansible-playbook implementations. This new RFE makes the ansible-runner the only available option.
Created redmine issue https://projects.theforeman.org/issues/27922 from this bug
by the following manual steps:
1) Check for the settings (that present in Sat6.6)
Administer -> Settings -> Ansible
Implementation for running Ansible: ansible-playbook <- this is missing at Sat6.7
>>> user no longer can choose between 'ansible-playbook' and 'ansible-runner'
2) Schedule Ansible REX command and while checking for processes running on satellite:
# watch "ps -efH | grep -A4 [a]nsible"
foreman+ 2667 15180 1 08:17 pts/5 00:00:00 /usr/bin/python2 /usr/bin/ansible-runner run /tmp/d20200206-15180-1pova5e -p playbook.yml
foreman+ 2675 2667 23 08:17 pts/6 00:00:01 /usr/bin/python2 /usr/bin/ansible-playbook -i /tmp/d20200206-15180-1pova5e/inventory playbook.yml
foreman+ 2723 2675 5 08:17 pts/6 00:00:00 /usr/bin/python2 /usr/bin/ansible-playbook -i /tmp/d20200206-15180-1pova5e/inventory playbook.yml
foreman+ 2787 2723 1 08:17 pts/6 00:00:00 ssh -o ProxyCommand=none -o StrictHostKeyChecking=no -o Port=22 -o IdentityFile="/usr/share/foreman-proxy/.ssh/id_rsa_foreman_proxy"...
>>> the manadatory implementation 'ansible-runner' is always used
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.