command_warnings fails in 2.3.0?

Archives Ansible Project
1

Hello,

It seems to me that command_warnings (http://docs.ansible.com/ansible/latest/intro_configuration.html#command-warnings )works fine with ansible-2.2.1.0 but not in 2.3.0.0 nor 2.3.1.0

Is anybody experiencing the same issue?

Stéphane

2

Can't confirm this with 2.3.1.0 since it's works in my test.

3

My test seems broken.
I think it works actually.

Sorry for spamming.

4

In fact, I think there is actually an issue in 2.3.0.0 and 2.3.1.0:

the warnings are removed from the ansible log of the control machine
but NOT from the syslog of the managed machines.

Stéphane

5

test with ansible 2.3.1.0 on Fedora 24:

ansible-playbook -i hosts test.yml

PLAY [all] ********************************************************************************************

TASK [command] ****************************************************************************************
changed: [localhost → localhost]

PLAY RECAP ********************************************************************************************
localhost : ok=1 changed=1 unreachable=0 failed=0

in /var/log/messages :
ansible-command[22445]: [WARNING] Consider using service module rather than running service

more *
::::::::::::::
ansible.cfg
::::::::::::::
[defaults]
command_warnings = False

::::::::::::::
hosts
::::::::::::::

localhost

::::::::::::::
test.yml
::::::::::::::