Bootstrap failed to complete: waiting for Kubernetes API: context deadline exceeded

[taosha121]

Version

$ openshift-install version
openshift-install4.2 v4.2.0
built from commit b5aebb52f4b363e942234cd7d7f1c145d044c2ef
release image quay.io/openshift-release-dev/ocp-release-nightly@sha256:75f065cf0590077ffba27ac61e104420660b8d2a344e09a11edd3cde50d14b01

Platform:

gcp

What happened?

Encountered the error that Bootstrap failed to complete: waiting for Kubernetes API: context deadline exceeded

What you expected to happen?

OCP cluster can be provisioned correctly on gcp platform.

How to reproduce it (as minimally and precisely as possible)?

1. download openshift-install v4.2 from https://mirror.openshift.com/pub/openshift-v4/clients/ocp-dev-preview/4.2.0-0.nightly-2019-10-07-203748/
2. generate a config yaml like what I attached through openshift-install create install-config
3. install cluster through openshift-install create cluster

$ openshift-install create install-config
$ openshift-install create cluster
DEBUG Apply complete! Resources: 73 added, 0 changed, 0 destroyed.
DEBUG OpenShift Installer v4.2.0
DEBUG Built from commit b5aebb52f4b363e942234cd7d7f1c145d044c2ef
INFO Waiting up to 30m0s for the Kubernetes API at https://api.marcotest.mcmlab.google.com:6443...
DEBUG Still waiting for the Kubernetes API: Get https://api.marcotest.mcmlab.google.com:6443/version?timeout=32s: dial tcp: lookup api.marcotest.mcmlab.google.com on 9.0.149.140:53: no such host
DEBUG Still waiting for the Kubernetes API: Get https://api.marcotest.mcmlab.google.com:6443/version?timeout=32s: dial tcp: lookup api.marcotest.mcmlab.google.com on 9.0.149.140:53: no such host
ERROR Attempted to gather debug logs after installation failure: failed to create SSH client, ensure the proper ssh key is in your keyring or specify with --key: ssh: handshake failed: EOF
FATAL Bootstrap failed to complete: waiting for Kubernetes API: context deadline exceeded

Anything else we need to know?

References

[taosha121]

The install log is here:
openshift_install.log

And my install-config.yaml is here:

apiVersion: v1
baseDomain: <my-base-domain>
compute:
- hyperthreading: Enabled
  name: worker
  platform: {}
  replicas: 3
controlPlane:
  hyperthreading: Enabled
  name: master
  platform: {}
  replicas: 3
metadata:
  creationTimestamp: null
  name: marcotest
networking:
  clusterNetwork:
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  machineCIDR: 10.0.0.0/16
  networkType: OpenShiftSDN
  serviceNetwork:
  - 172.30.0.0/16
platform:
  gcp:
    projectID: <my-project>
    region: us-east1
pullSecret: '<my-pull-secret>'

[taosha121]

@gyliu513 FYI.

[abhinavdahiya]

DEBUG Still waiting for the Kubernetes API: Get https://api.marcotest.mcmlab.google.com:6443/version?timeout=32s: dial tcp: lookup api.marcotest.mcmlab.google.com on 9.0.149.140:53: no such host

It looks like you are using a public zone that is not actually wired to the internet, or your machines doesn't have access to the records in that public zone mcmlab.google.com

[taosha121]

@abhinavdahiya , actually I am not familiar with google cloud and I am just following the instruction here to provision ocp cluster. Do you have any idea about how to check whether my public zone works well?

[gyliu513]

@xjtustt you can use the access key from @clyang82 , it works well.

[clyang82]

@abhinavdahiya Thanks for your comments. You are right.
@xjtustt follow this document we need to add nameserver to the openshift-installer host to resolve the managed zones(e.g.: mcmlab.google.com).

[abhinavdahiya]

@xjtustt follow this document we need to add nameserver to the openshift-installer host to resolve the managed zones(e.g.: mcmlab.google.com).

usually we recommend that the public zone be connected or resolvable from internet, but we can handle the resolutions on all clients, that's okay too.

also this looks like it's no longer anything the installer team might fix.

/close

[openshift-ci-robot]

@abhinavdahiya: Closing this issue.

Details

In response to this:

@xjtustt follow this document we need to add nameserver to the openshift-installer host to resolve the managed zones(e.g.: mcmlab.google.com).

usually we recommend that the public zone be connected or resolvable from internet, but we can handle the resolutions on all clients, that's okay too.

also this looks like it's no longer anything the installer team might fix.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.