https://github.com/openshift/ose/pull/847

Test on OCP3.4+rhel7.3 /OCP3.4+rhel7.4
oc v3.4.1.44.17
kubernetes v1.4.0+776c994
iptables v1.4.21

Use an infinite loop to keep creating services which have same endpoint from master side.

On the node side, check the process which is opening the /run/xtables.lock file.

[root@ip-172-18-1-166 ~]# while true ; do lsof +c0 /run/xtables.lock ; done
COMMAND            PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
iptables-restor 130893 root    3rW  REG   0,18        0 25053 /run/xtables.lock
COMMAND         PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
iptables-restor 438 root    3rW  REG   0,18        0 25053 /run/xtables.lock
COMMAND         PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
iptables-restor 451 root    3r   REG   0,18        0 25053 /run/xtables.lock
COMMAND         PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
iptables-restor 501 root    3r   REG   0,18        0 25053 /run/xtables.lock
COMMAND         PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
iptables-restor 530 root    3rW  REG   0,18        0 25053 /run/xtables.lock
COMMAND         PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
iptables-restor 559 root    3rW  REG   0,18        0 25053 /run/xtables.lock
COMMAND         PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
iptables-restor 630 root    3rW  REG   0,18        0 25053 /run/xtables.lock
COMMAND         PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
iptables-restor 645 root    3rW  REG   0,18        0 25053 /run/xtables.lock

And no "Resource temporarily unavailable (exit status 4)" in node log.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2670