Closed david-rh closed 3 years ago
Nice! That was the key to fixing the timeout issues from the machine controller during installation. Before: Installer:
FATAL failed to initialize the cluster: Some cluster operators are still updating: authentication, console, image-registry, ingress, monitoring
Machine API not able to bring up workers
E0715 23:18:45.967351 1 actuator.go:213] failed to check machine test-bntlv-worker-usgovvirginia3-kl52x exists: Failed to get vm: azure.BearerAuthorizer#WithAuthorization: Failed to refresh the Token for request to https://management.usgovcloudapi.net/subscriptions/adc59502-ab8c-4aa2-9203-44809b5c22ef/resourceGroups/test-bntlv-rg/providers/Microsoft.Compute/virtualMachines/test-bntlv-worker-usgovvirginia3-kl52x?%24expand=instanceView&api-version=2020-06-01: StatusCode=0 -- Original Error: adal: Failed to execute the refresh request. Error = 'Post "https://login.microsoftonline.us/fcbabb58-441c-4c58-bee9-cafbe16f16a9/oauth2/token?api-version=1.0": dial tcp 20.140.232.136:443: i/o timeout'
After:
INFO Waiting up to 10m0s for the openshift-console route to be created...
DEBUG Route found in openshift-console namespace: console
DEBUG OpenShift console route is admitted
INFO Install complete!
INFO To access the cluster as the system:admin user when using 'oc', run 'export KUBECONFIG=/home/azureuser/ocp_install/auth/kubeconfig'
INFO Access the OpenShift web-console here: https://console-openshift-console.apps.test.azuregov.sfxworks.net
INFO Login to the console with user: "kubeadmin", and password:
DEBUG Time elapsed per stage:
DEBUG Infrastructure: 12m21s
DEBUG Bootstrap Complete: 7m41s
DEBUG Bootstrap Destroy: 5m22s
DEBUG Cluster Operators: 11m39s
INFO Time elapsed: 37m10s
Recent testing revealed a key step missing from the firewall and route-table creation. Also, 4.7.10 has a known issue preventing install into AWS GovCloud, Note added to warn users.