Bug 1942122

Summary: Egress IP iptables rules not added due to iptables: Resource temporarily unavailable
Product: OpenShift Container Platform Reporter: Pablo Alonso Rodriguez <palonsor>
Component: NetworkingAssignee: Jacob Tanenbaum <jtanenba>
Networking sub component: openshift-sdn QA Contact: huirwang
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: aivaraslaimikis, anbhat, andbartl, jnordell, joboyer, jtanenba, openshift-bugs-escalate
Version: 3.11.0   
Target Milestone: ---   
Target Release: 4.9.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1979208 1979216 (view as bug list) Environment:
Last Closed: 2021-10-18 17:29:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1979208, 1979216, 1987239    

Description Pablo Alonso Rodriguez 2021-03-23 17:23:11 UTC 
Description of problem:

When applying iptables rules for an egress IP, sometimes the following error messages are shown and the rules are not applied


March 22nd 2021, 19:00:00.335	E0322 19:00:00.335303    5323 egressip.go:120] Error assigning Egress IP "10.x.x.x": could not add egress IP iptables rule: error appending rule: exit status 4: iptables: Resource temporarily unavailable.

Version-Release number of selected component (if applicable):

3.11.380

How reproducible:

Only in customer environment

Steps to Reproduce:

Customer reproduces it by restarting node or docker, but it might be reproducible by other means.

Actual results:

iptables rules for egress IPs not added, although OVS flows and other things are added.

Expected results:

iptables rules added as well

Additional info:

If I try to acquire a lock on xtables manually and then release it, I cannot reproduce this issue, because the iptables invocations from sdn are done with -w, so it just waits until I release the lock.
Comment 31 errata-xmlrpc 2021-10-18 17:29:21 UTC 
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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759
Comment 32 Red Hat Bugzilla 2023-09-15 01:03:54 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days