Document URL: https://github.com/openshift/installer/blob/master/docs/user/gcp/install_upi.md Section Number and Name: Describe the issue: 1. [Monitor for bootstrap-complete] step should be placed after [Pivot load balancers to control plane] step. If follow the steps in above doc, the "wait for bootstrap" step will fail due to temporary control plane teared down after bootstrap complete. But at that time, the api and int lb still target to bootstrap node. So the api can not access at all. And from the gcp console we can find that the lb of api and int are not healthy all the time. # ./openshift-install wait-for bootstrap-complete --dir test INFO Waiting up to 30m0s for the Kubernetes API at https://api.jliu.origin-gce.dev.openshift.com:6443... INFO Use the following commands to gather logs from the cluster INFO openshift-install gather bootstrap --help FATAL waiting for Kubernetes API: context deadline exceeded So do step [Pivot load balancers to control plane] to update the lb's instances. And then ran "wait for bootstrap" will succeed and curl https://api.jliu.origin-gce.dev.openshift.com:6443/ succeed. # gcloud compute target-pools add-instances ${INFRA_ID}-api-target-pool --instances-zone="${REGION}-d" --instances=${INFRA_ID}-m-0 Updated [https://www.googleapis.com/compute/v1/projects/openshift-gce-devel/regions/us-east1/targetPools/jliu-68n2v-api-target-pool]. # ./openshift-install wait-for bootstrap-complete --dir testINFO Waiting up to 30m0s for the Kubernetes API at https://api.jliu.origin-gce.dev.openshift.com:6443... INFO API v1.14.0+b7c8409 up INFO Waiting up to 30m0s for bootstrapping to complete... INFO It is now safe to remove the bootstrap resources Suggestions for improvement: Additional information:
I noticed the bug should be fixed in https://github.com/openshift/installer/commit/6f9230abda376b05969ecf0012f310c1969f07da#diff-6247f5de2172c3e64ed804505b299339 @Jeremiah Stuever Could u help update this bug's status?thx
This resolved with https://github.com/openshift/installer/pull/2289
LGTM, and it works now following the latest steps.
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:2922