Bug 1745907
Summary: | [upi-gcp] can not finish installation due to missing dns entry and lb for *.apps | ||
---|---|---|---|
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: | adahiya |
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:10:50 UTC
This seems like similar to what's being asked in https://bugzilla.redhat.com/show_bug.cgi?id=1715635 PR for the above one is https://github.com/openshift/installer/pull/2221 Just have a try on the latest 4.2.0-0.nightly-2019-08-29-041601, the ingress operator can generate the lb and *.apps records successfully without extra config this time. So i'not sure if it's a bug for ingress operator on 4.2.0-0.nightly-2019-08-21-235427 or just lukcy as https://bugzilla.redhat.com/show_bug.cgi?id=1715635#c5 said. So keep the bug open to track if extra steps needed for *.apps records on upi/gcp process. Since it's not blocking qe's test now, adjust severity and priority. Perhaps because of https://github.com/openshift/cluster-ingress-operator/pull/286 I just tried with latest from installer (master branch) and I still see the issue. The ingress-router load balancers are not getting created, probably because there are no compute nodes. The DNS entries are not created until the load balancers exist. Therefore, they rely on compute nodes to exist as well. Perhaps the "luck" is having added compute nodes to the cluster? I have a mostly ready PR to clarify how to add the compute nodes as well as how to add the apps DNS records manually. Will be posted as soon as I get it cleaned up. Version:4.2.0-0.nightly-2019-09-08-180038 Follow up latest doc https://github.com/openshift/installer/blob/master/docs/user/gcp/install_upi.md Before create iginition files, do https://github.com/openshift/installer/blob/master/docs/user/gcp/install_upi.md#remove-dns-zones-optional After bootstrap complete, do https://github.com/openshift/installer/blob/master/docs/user/gcp/install_upi.md#add-the-ingress-dns-records-optional # ./openshift-install wait-for install-complete INFO Waiting up to 30m0s for the cluster at https://api.jliu-4353.qe.gcp.devcluster.openshift.com:6443 to initialize... INFO Waiting up to 10m0s for the openshift-console route to be created... INFO Install complete! INFO To access the cluster as the system:admin user when using 'oc', run 'export KUBECONFIG=/root/work/upi_gcp/20190909_25655/auth/kubeconfig' INFO Access the OpenShift web-console here: https://console-openshift-console.apps.jliu-4353.qe.gcp.devcluster.openshift.com INFO Login to the console with user: kubeadmin, password: dLsAy-TLmX8-RtQZ5-WXawL # oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.2.0-0.nightly-2019-09-08-180038 True False 4m56s Cluster version is 4.2.0-0.nightly-2019-09-08-180038 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 |