# command\_warnings fails in 2.3.0?

**URL:** <https://forum.ansible.com/t/command-warnings-fails-in-2-3-0/25148>\
**Category:** Ansible Project\
**Created:** [August 1, 2017, 12:09pm UTC](https://forum.ansible.com/t/command-warnings-fails-in-2-3-0/25148 "2017-08-01T12:09:35Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stephane\_M](https://avatars.discourse-cdn.com/v4/letter/s/77aa72/32.png) [@Stephane\_M](https://forum.ansible.com/u/Stephane_M)\
**Post date:** [August 1, 2017, 12:09pm UTC](https://forum.ansible.com/t/command-warnings-fails-in-2-3-0/25148/1 "2017-08-01T12:09:35Z")

</div>

Hello,

It seems to me that command\_warnings ([http://docs.ansible.com/ansible/latest/intro\_configuration.html#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

---

<div class="post-metadata">

**Author:** ![Kai\_Stian\_Olstad](https://avatars.discourse-cdn.com/v4/letter/k/e19adc/32.png) [@Kai\_Stian\_Olstad](https://forum.ansible.com/u/Kai_Stian_Olstad)\
**Post date:** [August 1, 2017, 12:32pm UTC](https://forum.ansible.com/t/command-warnings-fails-in-2-3-0/25148/2 "2017-08-01T12:32:27Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Stephane\_M](https://avatars.discourse-cdn.com/v4/letter/s/77aa72/32.png) [@Stephane\_M](https://forum.ansible.com/u/Stephane_M)\
**Post date:** [August 1, 2017, 1:01pm UTC](https://forum.ansible.com/t/command-warnings-fails-in-2-3-0/25148/3 "2017-08-01T13:01:14Z")

</div>

My test seems broken.  
I think it works actually.

Sorry for spamming.

---

<div class="post-metadata">

**Author:** ![Stephane\_M](https://avatars.discourse-cdn.com/v4/letter/s/77aa72/32.png) [@Stephane\_M](https://forum.ansible.com/u/Stephane_M)\
**Post date:** [August 1, 2017, 1:30pm UTC](https://forum.ansible.com/t/command-warnings-fails-in-2-3-0/25148/4 "2017-08-01T13:30:52Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Stephane\_M](https://avatars.discourse-cdn.com/v4/letter/s/77aa72/32.png) [@Stephane\_M](https://forum.ansible.com/u/Stephane_M)\
**Post date:** [August 1, 2017, 1:49pm UTC](https://forum.ansible.com/t/command-warnings-fails-in-2-3-0/25148/5 "2017-08-01T13:49:35Z")

</div>

test with ansible [2.3.1.0](http://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  
::::::::::::::