Closed gregharvey closed 1 year ago
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark issues as stale.
This issue has been closed due to inactivity. If you feel this is in error, please reopen the issue or file a new issue with the relevant details.
This is related to this report here:
It was closed as not an Ansible issue, but this workaround mentioned there would apply:
I propose changing the handler so it does a kind of "fire and forget" restart like this, and perhaps a follow-up check to ensure the firewall came back up OK. That way we won't have to cancel hung Ansible processes whenever SSH gets stunned.