iptables errors in OpenShift - Resource temporarily unavailable (exit status 4)

Solution Verified - Updated -

Issue

  • We upgraded our OCP Clusters to 3.3. We also set the iptablesSyncPeriod to 30s and restarted the atomic-openshift-node daemon. Still we see the following iptables messages in the logs of the nodes.
Apr 24 09:30:48 nodeA atomic-openshift-node: E0424 09:30:48.529084   19598 node_iptables.go:64] Syncing openshift iptables failed: Failed to ensure rule {nat POSTROUTING [-s 10.1.0.0/16 ! -d 10.1.0.0/16 -j MASQUERADE]} exists: error checking rule: exit status 4: iptables: Resource temporarily unavailable.
Apr 24 09:46:47 nodeA atomic-openshift-node: E0424 09:46:47.799545   29189 node_iptables.go:64] Syncing openshift iptables failed: Failed to ensure rule {nat POSTROUTING [-s 10.1.0.0/16 ! -d 10.1.0.0/16 -j MASQUERADE]} exists: error checking rule: exit status 4: iptables: Resource temporarily unavailable.
  • xtables lock is not released, preventing iptables from updating
Another app is currently holding the xtables lock; waiting (9s) for it to exit...
Another app is currently holding the xtables lock; waiting (11s) for it to exit...

Environment

  • Red Hat OpenShift Enterprise
    • 3.2
  • Red Hat OpenShift Container Platform
    • 3.3
    • 3.4
    • 3.5
    • 3.6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content