Problem:
The Foreman callback plug-in is saying that requests is not installed therefore no systems are getting updated/registered via Ansible.
Expected outcome:
Foreman callback plug-in to update hosts information via Ansible.
Foreman and Proxy versions:
Foreman 3.1.2
Foreman and Proxy plugin versions:
Ansible 3
Distribution and version:
Centos 8 stream
Other relevant information:
python3-requests RPM is installed from upstream, removing that and substituting with python3 -m pip installed requests did not change the outcome.
It had nothing other then the comments, I added the defaults and callback section manuly
# Since Ansible 2.12 (core):
# To generate an example config file (a "disabled" one with all default settings, commented out):
# $ ansible-config init --disabled > ansible.cfg
#
# Also you can now have a more complete file by including existing plugins:
# ansible-config init --disabled -t all > ansible.cfg
# For previous versions of Ansible you can check for examples in the 'stable' branches of each version
# Note that this file was always incomplete and lagging changes to configuration settings
# for example, for 2.9: https://github.com/ansible/ansible/blob/stable-2.9/examples/ansible.cfg
Ahh I see, I was a bit confused based on the documentation Ansiblecallback it made it seem that /etc/ansible/ansible.cfg was still the main file that the configs needed to be in.
On the other there are two major ways of using the callback:
via the Foreman Ansible integration, which is setup automatically for you if you’re using the installer and uses /etc/foreman-proxy/ansible.cfg
manually from essentially any system that can run Ansible (and thus reads /etc/ansible/ansible.cfg)
In most cases, users want the former. The later is relevant if you have a separate environment to run Ansible from (AWX, Rundeck, whatever) and still want the reports be available in Foreman.