I suspect I am missing something simple, but when I try to use the awall module to establish firewall rules on Alpine Linux, ansible hangs on the awall activate task, even though allowing ssh is one of the rules I active. If I ssh to the machine before running the task, the connection remains intact, and I can establish new ssh connections as expected. It is only the ansible connection that seems to get interrupted, but it does successfully populate iptables rules via awall. Furthermore, I do not see the ansible activate task in /var/log/messages. I'm guessing this is because the ssh connection gets broken by the firewall. I am using ansible 2.9.6 and awall 1.7.1-r0, and Alpine Linux 3.11.3 (will try on 3.11.5 soon). Is this just an unavoidable limitation due to the way awall activates, making it impossible to use ansible to configure awall from the ground up?
-- 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 view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/cfaaed80-323b-494a-aa2d-4b176a02daf7%40googlegroups.com.
