Project

General

Profile

Bug #25274

Custom ansible.yml is not being used

Added by Paul Calabro about 2 years ago. Updated about 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

It appears that settings in /etc/foreman-proxy/settings.d/ansible.yml are not being used.
I'm customized the file as such:

:enabled: https
:ansible_dir: /usr/share/foreman-proxy
:working_dir: /etc/ansible/working_dir

and restarted foreman, foreman-proxy, and httpd (I'm assuming it's just foreman-proxy that needs to be bounced, however, I did this just in case)

However, the temporary playbook files are still created in /tmp.

History

#1 Updated by Paul Calabro about 2 years ago

  • Subject changed from Custom to Custom ansible.yml is not being used

Also available in: Atom PDF