This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2021-05-21 06:39
Elapsed27m3s
Revisionmaster

No Test Failures!


Error lines from build-log.txt

... skipping 669 lines ...
# Get kubeconfig and store it locally.
kubectl get secrets capz-9g3c9w-kubeconfig -o json | jq -r .data.value | base64 --decode > ./kubeconfig
timeout --foreground 600 bash -c "while ! kubectl --kubeconfig=./kubeconfig get nodes | grep master; do sleep 1; done"
Unable to connect to the server: dial tcp 20.84.168.83:6443: i/o timeout
Unable to connect to the server: dial tcp 20.84.168.83:6443: i/o timeout
Unable to connect to the server: dial tcp 20.84.168.83:6443: i/o timeout
make[1]: *** [Makefile:490: create-workload-cluster] Error 124
make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make: *** [Makefile:511: create-cluster] Error 2
================ DUMPING LOGS FOR MANAGEMENT CLUSTER ================
Unable to connect to the server: dial tcp 20.84.168.83:6443: i/o timeout
Exported logs for cluster "capz" to:
/logs/artifacts/management-cluster
================ DUMPING LOGS FOR WORKLOAD CLUSTER ================
Deploying log-dump-daemonset
Unable to connect to the server: dial tcp 20.84.168.83:6443: i/o timeout
error: unable to recognize "./scripts/../hack/log/../../hack/log/log-dump-daemonset.yaml": Get "https://capz-9g3c9w-c2d2cce5.centralus.cloudapp.azure.com:6443/api?timeout=32s": dial tcp 20.84.168.83:6443: i/o timeout
================ REDACTING LOGS ================
All sensitive variables are redacted
cluster.cluster.x-k8s.io "capz-9g3c9w" deleted
kind delete cluster --name=capz || true
Deleting cluster "capz" ...
kind delete cluster --name=capz-e2e || true
... skipping 11 lines ...