Bug 1634151

Summary: [3.11.z] CRI-O cluster install with openshift-ansible fails on large AWS instances m5.12xlarge and m4.16xlarge due to Master node openshift-sdn pod in CrashLoopBackOff state
Product: OpenShift Container Platform Reporter: Ben Bennett <bbennett>
Component: NetworkingAssignee: Casey Callendrello <cdc>
Status: CLOSED ERRATA QA Contact: Walid A. <wabouham>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.11.0CC: aconole, aos-bugs, bbennett, bmeng, cdc, danw, dcbw, jokerman, mifiedle, mmccomas, pcameron, wabouham, weliang, wmeng, zzhao
Target Milestone: ---   
Target Release: 3.11.z   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1633892 Environment:
Last Closed: 2019-06-06 02:00:28 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: 1633892    
Bug Blocks:    

Comment 3 zhaozhanqi 2019-04-16 09:28:26 UTC 
@Walid
 Can you help try this bug on the fixed version and verify this bug?
Comment 4 Walid A. 2019-04-17 20:01:40 UTC 
Verified this issue on OCP v3.11.106.  Please see https://bugzilla.redhat.com/show_bug.cgi?id=1633892
Comment 6 errata-xmlrpc 2019-06-06 02:00:28 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/RHBA-2019:0794