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

Bug 1745909

Summary:	[upi-gcp] control plane needs to be added to lb before "Monitor for bootstrap-complete"
Product:	OpenShift Container Platform	Reporter:	liujia <jiajliu>
Component:	Installer	Assignee:	Jeremiah Stuever <jstuever>
Installer sub component:	openshift-installer	QA Contact:	liujia <jiajliu>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	aos-bugs, jokerman
Version:	4.2.0
Target Milestone:	---
Target Release:	4.2.0
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-10-16 06:37:54 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:

Description liujia 2019-08-27 08:15:01 UTC

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:

Comment 1 liujia 2019-09-09 05:45:19 UTC

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

Comment 2 Jeremiah Stuever 2019-09-09 16:47:17 UTC

This resolved with https://github.com/openshift/installer/pull/2289

Comment 4 liujia 2019-09-11 06:36:10 UTC

LGTM, and it works now following the latest steps.

Comment 5 errata-xmlrpc 2019-10-16 06:37:54 UTC

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