# Ansible firewalld-module: Avoiding useless errors when firewalld is not running during check\_mode

**URL:** <https://forum.ansible.com/t/ansible-firewalld-module-avoiding-useless-errors-when-firewalld-is-not-running-during-check-mode/21441>\
**Category:** Ansible Project\
**Created:** [May 14, 2016, 8:06pm UTC](https://forum.ansible.com/t/ansible-firewalld-module-avoiding-useless-errors-when-firewalld-is-not-running-during-check-mode/21441 "2016-05-14T20:06:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Johannes\_Kastl](https://avatars.discourse-cdn.com/v4/letter/j/bbe5ce/32.png) [@Johannes\_Kastl](https://forum.ansible.com/u/Johannes_Kastl)\
**Post date:** [May 14, 2016, 8:06pm UTC](https://forum.ansible.com/t/ansible-firewalld-module-avoiding-useless-errors-when-firewalld-is-not-running-during-check-mode/21441/1 "2016-05-14T20:06:34Z")

</div>

Hi all,

ansible's firewalld-module is kinda picky when it comes to testing.

To work it needs a started firewalld. Even in check mode.

So if I test my playbook which installs firewalld, starts it and then  
does some stuff, it errors out because firewalld is not running (as it  
is not being installed as I am still in check mode). Get it?

This is stupid, as I cannot do the actual installation and starting of  
firewalld just to avoid errors during testing.

How to workaround this? Why is this module implemented in such a  
nitpicking way?

Frustrated,

Johannes