New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iptables lock issue #38106
iptables lock issue #38106
Conversation
Actually, older versions of iptables are incompatible with this option. I think Debian 7 is in this case. I agree with you, this option important. Maybe we could check the version of iptables, or try without "-w" if the command fails ? |
The test
The test
The test
The test
The test
The test
|
CI failure in unit tests: https://app.shippable.com/github/ansible/ansible/runs/60448/3/tests |
@mattclay Seems to be unit tests should be fixed to reflect the new |
@akamac Yes, the unit tests will need to be updated as part of this PR. |
@akamac this PR contains the following merge commits: Please rebase your branch to remove these commits. |
The test
The test
The test
The test
The test
The test
|
consider making this a module option, I would not accept it in it's current state as it is both backwards incompatible with older iptables and changes the default behaviour of the module. needs_info |
Closing in favor of #47877 |
SUMMARY
When adding multiple rules in a loop it is possible to get lock error.
-w switch fixes this:
--wait -w [seconds] wait for the xtables lock
ISSUE TYPE
COMPONENT NAME
iptables module
ANSIBLE VERSION
ansible 2.6.0 (fix c1aac04495)
ADDITIONAL INFORMATION
Added -w as default parameter.