Bug 1669812

Summary: Installer failed with error: FATAL waiting for Kubernetes API: context deadline exceeded
Product: OpenShift Container Platform Reporter: Neeraj <nbhatt>
Component: InstallerAssignee: Alex Crawford <crawford>
Installer sub component: openshift-installer QA Contact: Johnny Liu <jialiu>
Status: CLOSED INSUFFICIENT_DATA Docs Contact:
Severity: medium    
Priority: unspecified CC: aos-bugs, crawford, jokerman, mmccomas, nbhatt, sdodson, wking
Version: 4.1.0   
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-18 18:54:15 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:    
Bug Blocks: 1664187    

Description Neeraj 2019-01-27 10:15:19 UTC
Description of problem:

Trying to install with the instanceType T2.medium and failing with error. 

FATAL waiting for Kubernetes API: context deadline exceeded

How reproducible:

1> Set the instance type to t2.medium in install-confing

~~~
...
  platform:
    aws:
      type: t2.medium
...
~~~

2> Run installer 
  ./openshift-install --dir=ocp4 create cluster

Actual results:
INFO Consuming "Openshift Manifests" from target directory 
INFO Consuming "DNS Config" from target directory 
INFO Consuming "Ingress Config" from target directory 
INFO Consuming "Network Config" from target directory 
INFO Consuming "Common Manifests" from target directory 
INFO Consuming "Kubeconfig Admin" from target directory 
INFO Creating cluster...                          
INFO Waiting up to 30m0s for the Kubernetes API... 
FATAL waiting for Kubernetes API: context deadline exceeded 

Expected results:

Cluster should be up and running

Comment 4 Alex Crawford 2019-02-13 22:16:44 UTC
The master team has introduced a number of fixes since this defect was filed. Could you try a newer version and let us know if it's still having trouble?

Comment 5 Alex Crawford 2019-02-18 18:54:15 UTC
Closing due to inactivity.