This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2022-07-11 19:47
Elapsed53m25s
Revisionrelease-1.4

No Test Failures!


Error lines from build-log.txt

... skipping 635 lines ...
certificate.cert-manager.io "selfsigned-cert" deleted
# Create secret for AzureClusterIdentity
./hack/create-identity-secret.sh
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make[2]: Nothing to be done for 'kubectl'.
make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
Error from server (NotFound): secrets "cluster-identity-secret" not found
secret/cluster-identity-secret created
secret/cluster-identity-secret labeled
# Create customized cloud provider configs
./hack/create-custom-cloud-provider-config.sh
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make[2]: Nothing to be done for 'kubectl'.
... skipping 138 lines ...
timeout --foreground 300 bash -c "while ! /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 get secrets | grep capz-ryrdso-kubeconfig; do sleep 1; done"
capz-ryrdso-kubeconfig                 cluster.x-k8s.io/secret   1      1s
# Get kubeconfig and store it locally.
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 get secrets capz-ryrdso-kubeconfig -o json | jq -r .data.value | base64 --decode > ./kubeconfig
timeout --foreground 600 bash -c "while ! /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 --kubeconfig=./kubeconfig get nodes | grep control-plane; do sleep 1; done"
Unable to connect to the server: dial tcp 20.99.200.41:6443: i/o timeout
error: the server doesn't have a resource type "nodes"
capz-ryrdso-control-plane-tpxd7   NotReady   <none>   3s    v1.22.12-rc.0.25+666c9008e8be22
run "/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kubectl-v1.22.4 --kubeconfig=./kubeconfig ..." to work with the new target cluster
make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
Waiting for 1 control plane machine(s), 2 worker machine(s), and  windows machine(s) to become Ready
NAME                              STATUS   ROLES                  AGE   VERSION                           INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION     CONTAINER-RUNTIME
capz-ryrdso-control-plane-tpxd7   Ready    control-plane,master   30m   v1.22.12-rc.0.25+666c9008e8be22   10.0.0.4      <none>        Ubuntu 18.04.6 LTS   5.4.0-1085-azure   containerd://1.6.2
... skipping 15 lines ...
INFO: Creating log watcher for controller capz-system/capz-controller-manager, pod capz-controller-manager-59596978b5-jnq4l, container manager
STEP: Dumping workload cluster default/capz-ryrdso logs
Jul 11 20:33:57.680: INFO: Collecting logs for Linux node capz-ryrdso-control-plane-tpxd7 in cluster capz-ryrdso in namespace default

Jul 11 20:34:57.682: INFO: Collecting boot logs for AzureMachine capz-ryrdso-control-plane-tpxd7

Failed to get logs for machine capz-ryrdso-control-plane-t79sd, cluster default/capz-ryrdso: open /etc/azure-ssh/azure-ssh: no such file or directory
Failed to get logs for machine capz-ryrdso-md-0-8645566fdf-5fnqq, cluster default/capz-ryrdso: azuremachines.infrastructure.cluster.x-k8s.io "capz-ryrdso-md-0-brsxj" not found
Failed to get logs for machine capz-ryrdso-md-0-8645566fdf-wfdtb, cluster default/capz-ryrdso: azuremachines.infrastructure.cluster.x-k8s.io "capz-ryrdso-md-0-2t8jd" not found
STEP: Dumping workload cluster default/capz-ryrdso kube-system pod logs
STEP: Fetching kube-system pod logs took 733.365516ms
STEP: Dumping workload cluster default/capz-ryrdso Azure activity log
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-mzdx5, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-mzdx5
STEP: Creating log watcher for controller kube-system/calico-node-n4hg2, container calico-node
STEP: Collecting events for Pod kube-system/calico-node-n4hg2
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-5mwvq, container coredns
STEP: Creating log watcher for controller kube-system/kube-controller-manager-capz-ryrdso-control-plane-tpxd7, container kube-controller-manager
STEP: Collecting events for Pod kube-system/kube-controller-manager-capz-ryrdso-control-plane-tpxd7
STEP: failed to find events of Pod "kube-controller-manager-capz-ryrdso-control-plane-tpxd7"
STEP: Creating log watcher for controller kube-system/kube-proxy-mcjrc, container kube-proxy
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-5mwvq
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-9cgkm, container coredns
STEP: Collecting events for Pod kube-system/etcd-capz-ryrdso-control-plane-tpxd7
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-9cgkm
STEP: Collecting events for Pod kube-system/kube-scheduler-capz-ryrdso-control-plane-tpxd7
STEP: Creating log watcher for controller kube-system/etcd-capz-ryrdso-control-plane-tpxd7, container etcd
STEP: Collecting events for Pod kube-system/metrics-server-8c95fb79b-r4mzt
STEP: failed to find events of Pod "kube-scheduler-capz-ryrdso-control-plane-tpxd7"
STEP: Collecting events for Pod kube-system/kube-proxy-mcjrc
STEP: Collecting events for Pod kube-system/kube-apiserver-capz-ryrdso-control-plane-tpxd7
STEP: Creating log watcher for controller kube-system/kube-apiserver-capz-ryrdso-control-plane-tpxd7, container kube-apiserver
STEP: Creating log watcher for controller kube-system/metrics-server-8c95fb79b-r4mzt, container metrics-server
STEP: Creating log watcher for controller kube-system/kube-scheduler-capz-ryrdso-control-plane-tpxd7, container kube-scheduler
STEP: Fetching activity logs took 4.119606416s
... skipping 17 lines ...