# Command module fails on skip?

**URL:** <https://forum.ansible.com/t/command-module-fails-on-skip/11865>\
**Category:** Ansible Project\
**Tags:** ansible-project\
**Created:** [September 6, 2012, 12:59am UTC](https://forum.ansible.com/t/command-module-fails-on-skip/11865 "2012-09-06T00:59:58Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [September 6, 2012, 12:59am UTC](https://forum.ansible.com/t/command-module-fails-on-skip/11865/1 "2012-09-06T00:59:58Z")

</div>

Good catch -- I've just pushed a fix for this. Seems no one was  
using creates= combined with /usr/bin/ansible and not a playbook,  
which is not surprising. In fixing this, I also ended up updating the  
log\_plays.py callbacks in the example callbacks repo. If anyone has  
any existing custom callbacks, you too many need to make some updates.

I also noticed if a command module results in a skipped from  
/usr/bin/ansible it doesn't produce any output, but since playbooks  
already do, I'm going to consider that a minor bug and file that one  
for the 0.8 release.

--Michael