Description of problem: Deploying default templates in OpenShift Dev Preview, e.g., nodejs-mongo-persistent or laravel-mysql-example causing confusing error messages in Event Monitoring. The error message is: Error syncing pod, skipping: failed to "SetupNetwork" for "mysql-1-deploy_wgordon-test" with SetupNetworkError: "Failed to setup network for pod \"mysql-1-deploy_wgordon-test(808a01b7-f7a7-11e6-9235-0e63b9c1c48f)\" using network plugins \"cni\": CNI request failed with status 400: 'Failed to ensure that nat chain POSTROUTING jumps to MASQUERADE: error checking rule: exit status 4: iptables: Resource temporarily unavailable.\n\n'; Skipping pod" This seems to cause no actual degradation of service, and only leads to the assumption that our default templates are somehow broken. Version-Release number of selected component (if applicable): v3.4.1.2 (online version 3.4.0.13) How reproducible: always Steps to Reproduce: 1. Start a new project 2. Select "nodejs-mongo-persistent" to add to your project 3. Watch the Monitoring > Events page Actual results: Successful deployment with error message that apparently has no bearing on the outcome Expected results: Always successful, or errors with a "real" error message that requires the template owner to fix Additional info: Occurs in both -build and -deploy pods
I have gotten a patch accepted upstream to iptables that will prevent this error report from iptables when checking rules. But this patch doesn't solve the problem of contention in the kernel that is the actual cause here. We somehow need to figure out what two iptables processes are doing stuff at the same time, and which one isn't properly waiting for the other to finish. Are you able to reliably reproduce this issue?