*** Bug 1773687 has been marked as a duplicate of this bug. ***
Verify this bug with 4.3.0-0.nightly-2019-11-21-230534.
# ./openshift-install version
built from commit a702fd4beb593932067fe1b31f2d911feaa6d93e
release image registry.svc.ci.openshift.org/ocp/release@sha256:15132234d0b753aea0af00f5cfff429cf5eca57513e7cce530207b05167a999f
Install a private cluster out of the cluster VPC, no panics when trying to gather logs.
# ./openshift-install create cluster --dir gpei-2
INFO Consuming Install Config from target directory
INFO Creating infrastructure resources...
INFO Waiting up to 30m0s for the Kubernetes API at https://api.gpei-2.qe.gcp.devcluster.openshift.com:6443...
ERROR Attempted to gather ClusterOperator status after installation failure: listing ClusterOperator objects: Get https://api.gpei-2.qe.gcp.devcluster.openshift.com:6443/apis/config.openshift.io/v1/clusteroperators: dial tcp: lookup api.gpei-2.qe.gcp.devcluster.openshift.com on 10.11.5.19:53: no such host
INFO Pulling debug logs from the bootstrap machine
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: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
FATAL Bootstrap failed to complete: waiting for Kubernetes API: context deadline exceeded
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.