Project

General

Profile

Actions
Copy link

Bug #25274

closed

Working dir in ansible.yml is not used

Added by Paul Calabro over 5 years ago. Updated almost 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
Difficulty:
easy
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

This is also customizable in installer

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.

Actions
Copy link
 #1

Updated by Paul Calabro over 5 years ago

  • Subject changed from Custom to Custom ansible.yml is not being used
Actions
Copy link
 #2

Updated by Ondřej Ezr about 3 years ago

  • Subject changed from Custom ansible.yml is not being used to Working dir in ansible.yml is not used
  • Difficulty set to easy
  • Triaged changed from No to Yes

We sould eighter remove the config, or use it to place the ansible-runner working files.

Actions
Copy link
 #3

Updated by Ondřej Ezr about 3 years ago

  • Description updated (diff)
Actions
Copy link
 #4

Updated by yifat makias almost 3 years ago

  • Status changed from New to Resolved
Actions
Copy link

Also available in: Atom PDF