Bug 1743587

Summary: Pods stuck in container creating - Failed to run CNI IPAM ADD: failed to allocate for range 0
Product: OpenShift Container Platform Reporter: Alexander Constantinescu <aconstan>
Component: NetworkingAssignee: Casey Callendrello <cdc>
Status: CLOSED ERRATA QA Contact: Weibin Liang <weliang>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 4.1.0CC: aconstan, aos-bugs, cdc, itbrown, nagrawal, veer, weliang, zzhao
Target Milestone: ---   
Target Release: 4.1.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1735538 Environment:
Last Closed: 2019-09-10 15:59:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1735538    
Bug Blocks:    

Comment 2 zhaozhanqi 2019-08-28 02:58:47 UTC
@weibin, Could you help verify this bug on 4.1 since I saw you verify this on 4.2. thanks

Comment 3 Weibin Liang 2019-08-28 15:40:32 UTC
Tested and verified on 4.1.0-0.nightly-2019-08-28-043410

Comment 5 errata-xmlrpc 2019-09-10 15:59:37 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, 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-2019:2594