Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1814814

Summary: OpenShift installer using installer-provisioned-infrastructure times out while waiting for the API to start.
Product: OpenShift Container Platform Reporter: Jon <joncp>
Component: InstallerAssignee: Abhinav Dahiya <adahiya>
Installer sub component: openshift-installer QA Contact: Johnny Liu <jialiu>
Status: CLOSED DUPLICATE Docs Contact:
Severity: high    
Priority: unspecified CC: joncp, tmckay
Version: 4.3.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: 2020-03-19 17:45:34 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:
Attachments:
Description Flags
debug-level command-line output of the installer session.
none
Debug Log Bundle none

Description Jon 2020-03-18 17:17:26 UTC
Created attachment 1671178 [details]
debug-level command-line output of the installer session.

Description of problem:

Version-Release number of the following components:
rpm -q openshift-ansible: (N/A, mac OpenShift installer)
rpm -q ansible: (N/A, mac OpenShift installer)
ansible --version: (N/A, mac OpenShift installer)

How reproducible:

Steps to Reproduce:
1. In the unpacked installer dir, run: openshift-install create cluster --dir=../../install/oc10 --log-level=debug
2. Answer the questions with an ssh key, platform: aws, region: us-east-2, as well as the cluster name and pull secret


Actual results:
When the installer gets to the stage that it is "Waiting up to 30m0s for the Kubernetes API at https://<the API>:6443..." it will time out.
Debug output attached to this bug as "log.txt"

Expected results:
The installer should complete successfully.

Additional info:
* First instinct is that DNS is misconfigured, but DNS seems to be working, since you can "ssh -v" to the API URL and see it trying the three master nodes' IP addresses.
* This exact behavior happens when we try to install v4.3.5 and v4.2.12 on both AWS and Azure.

Comment 1 Abhinav Dahiya 2020-03-18 17:29:40 UTC
On failure, the installer provides a log bundle for debugging.. can you please attach that?

Comment 2 Jon 2020-03-18 22:13:37 UTC
Created attachment 1671250 [details]
Debug Log Bundle

Comment 3 Jon 2020-03-19 17:44:55 UTC
After digging through the log bundle and googling some errors I found there, I determined that I was using a corrupted pull secret. I redownloaded it from redhat and the installation continues.

It seems that this was handled under 1662106 and closed as WONTFIX for some reason.

Comment 4 Jon 2020-03-19 17:45:34 UTC

*** This bug has been marked as a duplicate of bug 1662106 ***