Okd: Install OKD 4.6 on vSphere UPI failed

Created on 17 Dec 2020  Â·  3Comments  Â·  Source: openshift/okd

Describe the bug

openshift-install wait-for install-complete failed with message:

Cluster operator authentication Degraded is True with IngressStateEndpoints_MissingSubsets::OAuthRouteCheckEndpointAccessibleController_SyncError::OAuthServerDeployment_GetFailed::OAuthServiceCheckEndpointAccessibleController_SyncError::OAuthServiceEndpointsCheckEndpointAccessibleController_SyncError::OAuthVersionDeployment_GetFailed::Route_FailedGet: OAuthServiceEndpointsCheckEndpointAccessibleControllerDegraded: oauth service endpoints are not ready
OAuthServiceCheckEndpointAccessibleControllerDegraded: Get "https://172.30.181.54:443/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
IngressStateEndpointsDegraded: No subsets found for the endpoints of oauth-server
OAuthRouteCheckEndpointAccessibleControllerDegraded: Get "https://oauth-openshift.apps.okd4-spb.sigma-it.local/healthz": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
OAuthServerDeploymentDegraded: Unable to get "openshift-browser-client" bootstrapped CLI OAuth client: the server is currently unable to handle the request (post oauthclients.oauth.openshift.io)
RouteDegraded: Unable to get required route openshift-authentication/oauth-openshift: the server is currently unable to handle the request (get routes.route.openshift.io oauth-openshift)
OAuthVersionDeploymentDegraded: Unable to get OAuth server deployment: deployment.apps "oauth-openshift" not found"

$ oc get co
изображение

$ oc get nodes
изображение

$ oc get pods -n openshift-authentication
No resources found in openshift-authentication namespace.

Version
4.6.0-0.okd-2020-12-12-135354 on vSphere UPI

How reproducible
reproducible - 100%

Log bundle
must-gather

Most helpful comment

Get \"https://172.30.181.54:443/healthz\": dial tcp 172.30.181.54:443: i/o timeout (Client.Timeout exceeded while awaiting headers)

Seems OpenShiftSDN installs are broken - service won't reply

All 3 comments

Get \"https://172.30.181.54:443/healthz\": dial tcp 172.30.181.54:443: i/o timeout (Client.Timeout exceeded while awaiting headers)

Seems OpenShiftSDN installs are broken - service won't reply

With the OVNKubernetes network plugin, cluster was installed successfully.

Lets track this in #430

Was this page helpful?
0 / 5 - 0 ratings

Related issues

DanyC97 picture DanyC97  Â·  10Comments

devinmatte picture devinmatte  Â·  12Comments

llomgui picture llomgui  Â·  11Comments

kai-uwe-rommel picture kai-uwe-rommel  Â·  12Comments

vrutkovs picture vrutkovs  Â·  12Comments