Ansible已识别配置文件但设置被忽略，如何确保配置生效？

问题详情 #

我在ansible配置文件中添加了以下非默认配置：

log_path=./ansible_log.txt

# (boolean) Normally ``ansible-playbook`` will print a header for each task that is run. These headers will contain the name: field from the task if you specified one. If you didn't then ``ansible-playbook`` uses the task's action to help you tell which task is presently running. Sometimes you run many of the same action and so you want more information about the task to differentiate it from others of the same action. If you set this variable to True in the config then ``ansible-playbook`` will also include the task's arguments in the header.
# This setting defaults to False because there is a chance that you have sensitive values in your parameters and you do not want those to be printed.
# If you set this to True you should be sure that you have secured your environment's stdout (no one can shoulder surf your screen and you aren't saving stdout to an insecure file) or made sure that all of your playbooks explicitly added the ``no_log: True`` parameter to tasks which have sensitive values See How do I keep secret data in my playbook? for more information.
display_args_to_stdout=True

# (boolean) Set this to "False" if you want to avoid host key checking by the underlying tools Ansible uses to connect to the host
host_key_checking=False


# (string) Set the main callback used to display Ansible output. You can only have one at a time.
# You can have many other callbacks, but just one can be in charge of stdout.
# See :ref:`callback_plugins` for a list of available options.
;stdout_callback=default

callbacks_enabled=ansible.posix.profile_tasks, ansible.posix.timer

在执行Playbook的同一目录下运行ansible --version，输出显示：

ansible [core 2.15.3]

config file = /home/my_name/repos/some_repo/dev/ansible.cfg

通过cat /home/my_name/repos/some_repo/dev/ansible.cfg可确认配置文件内容与上述一致。

Ansible已识别该配置文件，但配置设置未生效：未生成日志，也看不到回调插件的额外输出。请问如何确保ansible.cfg中的配置不被忽略？

排查与解决步骤 #

1. 确认配置项的适用范围与路径 #

• log_path：相对路径是基于命令执行时的工作目录，而非配置文件所在目录。要么切换到配置文件所在目录执行Playbook，要么将路径改为绝对路径（如/home/my_name/repos/some_repo/dev/ansible_log.txt）。
• callbacks_enabled：仅对ansible-playbook命令生效，对ansible单命令无效，必须通过执行完整Playbook测试插件输出。

2. 验证依赖插件是否安装 #

ansible.posix.profile_tasks和ansible.posix.timer属于ansible.posix集合，需确认已安装：

ansible-galaxy collection list ansible.posix

如果未安装，执行以下命令安装：

ansible-galaxy collection install ansible.posix

3. 检查实际加载的配置值 #

执行命令查看Ansible实际生效的非默认配置，确认你的设置是否被加载：

ansible-config dump --only-changed

如果目标配置项未出现在输出中，说明存在优先级更高的配置覆盖了当前文件。

4. 排查配置优先级冲突 #

Ansible配置读取优先级从高到低为：

• 命令行参数（如--log-path、--skip-host-key-checking）
• 环境变量（如ANSIBLE_LOG_PATH、ANSIBLE_HOST_KEY_CHECKING）
• 当前目录下的ansible.cfg
• 用户家目录.ansible.cfg
• 系统级/etc/ansible/ansible.cfg

执行以下命令检查是否存在覆盖配置的环境变量：

env | grep ANSIBLE_

若存在对应环境变量，需删除或修改以避免覆盖配置文件设置。

5. 逐项测试配置有效性 #

• 测试host_key_checking：连接新主机，若未提示主机密钥验证，说明该项已生效。
• 测试log_path：执行ansible localhost -m ping，检查指定路径是否生成日志文件。
• 测试回调插件：执行Playbook时添加-v参数，观察是否出现任务耗时统计、总执行时间等插件输出。

内容的提问来源于stack exchange，提问作者Sven van den Boogaart