Bug 1810505
Summary: | Failed create pod sandbox due to sandbox already exists | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> |
Component: | Networking | Assignee: | Dan Winship <danw> |
Networking sub component: | openshift-sdn | QA Contact: | zhaozhanqi <zzhao> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | aconstan |
Version: | 4.2.z | Keywords: | Regression |
Target Milestone: | --- | ||
Target Release: | 4.5.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Cause: iptables locking problems
Consequence: In rare circumstances, a pod could fail to start, and "oc describe pod" would show an event including the text "Failed create pod sandbox ... could not set up pod iptables rules: Another app is currently holding the xtables lock."
Fix: We now pass "-w" to iptables in the relevant piece of code
Result: iptables waits for the lock, does not fail spuriously.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2020-08-04 18:03:44 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: |
Description
Junqi Zhao
2020-03-05 11:58:10 UTC
verified this bug on 4.5.0-0.nightly-2020-03-10-002435 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 (OpenShift Container Platform 4.5 image release 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-2020:2409 |