# Skip or fail in check mode with missing dependencies?

**URL:** <https://forum.ansible.com/t/skip-or-fail-in-check-mode-with-missing-dependencies/20397>\
**Category:** Ansible Developer\
**Created:** [February 1, 2016, 10:14am UTC](https://forum.ansible.com/t/skip-or-fail-in-check-mode-with-missing-dependencies/20397 "2016-02-01T10:14:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mattclay](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mattclay/32/268_2.png) [@mattclay](https://forum.ansible.com/u/mattclay)\
**Post date:** [February 1, 2016, 10:14am UTC](https://forum.ansible.com/t/skip-or-fail-in-check-mode-with-missing-dependencies/20397/1 "2016-02-01T10:14:47Z")

</div>

When running in check mode, should a module report skipped or failed if it has dependencies which cannot be satisfied?

For example, the apt\_repository module requires python-apt, which it will automatically install, except in check mode.

Reporting failed allows the module to explain why it can’t function. Skipped seems more appropriate, but there doesn’t appear to be a way to provide a skipped reason.

Issue: [https://github.com/ansible/ansible/issues/13520](https://github.com/ansible/ansible/issues/13520)  
PR: [https://github.com/ansible/ansible-modules-core/pull/2925](https://github.com/ansible/ansible-modules-core/pull/2925)

- Matt Clay