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

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/5737854A.3080503%40ojkastl.de.
For more options, visit https://groups.google.com/d/optout.

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to