commit 5a65e974d5cf0b302a59cab41c7d3b537862ac75
Author: Brian Haley <email address hidden>
Date: Wed Oct 18 15:38:29 2017 -0400
Always call iptables-restore with -w if done once
In the case where we called iptables-restore with a
-w argument and it succeeded, we should short-circuit
future calls to always use -w, instead of trying
without it, just to fall-back to using it on failure.
While analyzing some l3-agent log files I have seen
lots of "Perhaps you want to use the -w option?",
followed by a call with -w, followed by not using it
the next time. Changing this can save one failing
call to iptables-restore.
Change-Id: Icac99eb1d43648c64b6beaee0d6201f990eacb51
Related-bug: #1712185
(cherry picked from commit 6c50ad5858175e2eddeed7a3e28cf8b53c2eb2b3)
Reviewed: https:/ /review. openstack. org/515488 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=5a65e974d5c f0b302a59cab41c 7d3b537862ac75
Committed: https:/
Submitter: Zuul
Branch: stable/pike
commit 5a65e974d5cf0b3 02a59cab41c7d3b 537862ac75
Author: Brian Haley <email address hidden>
Date: Wed Oct 18 15:38:29 2017 -0400
Always call iptables-restore with -w if done once
In the case where we called iptables-restore with a
-w argument and it succeeded, we should short-circuit
future calls to always use -w, instead of trying
without it, just to fall-back to using it on failure.
While analyzing some l3-agent log files I have seen
lots of "Perhaps you want to use the -w option?",
followed by a call with -w, followed by not using it
the next time. Changing this can save one failing
call to iptables-restore.
Change-Id: Icac99eb1d43648 c64b6beaee0d620 1f990eacb51 eddeed7a3e28cf8 b53c2eb2b3)
Related-bug: #1712185
(cherry picked from commit 6c50ad5858175e2