Otherwise, ~foreman-proxy/.ansible.cfg settings are ignored when running Ansible jobs.
Created from redmine issue http://projects.theforeman.org/issues/23905
Upstream bug assigned to None
Description of problem: Any setting in /etc/foreman-proxy/ansible.cfg is ignored and only global system config /etc/ansible/ansible.cfg is applied Actual results: rex job stuck at host key check although host_key_checking = False in /etc/foreman-proxy/ansible.cfg Expected results: any setting (in /etc/foreman-proxy/ansible.cfg) overriding global setting (in /etc/ansible/ansible.cfg) is respected within foreman-proxy realm
^ disregard Actual results:
Upstream bug assigned to dlobatog
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/23905 has been resolved.
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. https://access.redhat.com/errata/RHSA-2018:2927