This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2022-09-02 09:24
Elapsed50m29s
Revisionmain

No Test Failures!


Error lines from build-log.txt

... skipping 701 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 141 lines ...
# Wait for the kubeconfig to become available.
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-0iy3pb-kubeconfig; do sleep 1; done"
capz-0iy3pb-kubeconfig                 cluster.x-k8s.io/secret   1      0s
# 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-0iy3pb-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"
error: the server doesn't have a resource type "nodes"
capz-0iy3pb-control-plane-mwnxm   NotReady   control-plane   7s    v1.26.0-alpha.0.358+baf6014e0c8710
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-0iy3pb-control-plane-mwnxm   Ready    control-plane   30m   v1.26.0-alpha.0.358+baf6014e0c8710   10.0.0.4      <none>        Ubuntu 18.04.6 LTS   5.4.0-1089-azure   containerd://1.6.2
... skipping 15 lines ...
INFO: Creating log watcher for controller capz-system/capz-controller-manager, pod capz-controller-manager-858df9cd95-r44jp, container manager
STEP: Dumping workload cluster default/capz-0iy3pb logs
Sep  2 10:06:20.743: INFO: Collecting logs for Linux node capz-0iy3pb-control-plane-mwnxm in cluster capz-0iy3pb in namespace default

Sep  2 10:07:20.745: INFO: Collecting boot logs for AzureMachine capz-0iy3pb-control-plane-mwnxm

Failed to get logs for machine capz-0iy3pb-control-plane-6m77b, cluster default/capz-0iy3pb: open /etc/azure-ssh/azure-ssh: no such file or directory
Sep  2 10:07:22.117: INFO: Collecting logs for Linux node capz-0iy3pb-md-0-5d4gz in cluster capz-0iy3pb in namespace default

Sep  2 10:08:22.118: INFO: Collecting boot logs for AzureMachine capz-0iy3pb-md-0-5d4gz

Failed to get logs for machine capz-0iy3pb-md-0-6544b7ff9b-78875, cluster default/capz-0iy3pb: [open /etc/azure-ssh/azure-ssh: no such file or directory, Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil]
Sep  2 10:08:22.141: INFO: Collecting logs for Linux node capz-0iy3pb-md-0-j48h6 in cluster capz-0iy3pb in namespace default

Sep  2 10:09:22.145: INFO: Collecting boot logs for AzureMachine capz-0iy3pb-md-0-j48h6

Failed to get logs for machine capz-0iy3pb-md-0-6544b7ff9b-bgtgt, cluster default/capz-0iy3pb: [open /etc/azure-ssh/azure-ssh: no such file or directory, Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil]
STEP: Dumping workload cluster default/capz-0iy3pb kube-system pod logs
STEP: Fetching kube-system pod logs took 706.216841ms
STEP: Dumping workload cluster default/capz-0iy3pb Azure activity log
STEP: Collecting events for Pod kube-system/kube-controller-manager-capz-0iy3pb-control-plane-mwnxm
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-755ff8d7b5-sknlr, container calico-kube-controllers
STEP: failed to find events of Pod "kube-controller-manager-capz-0iy3pb-control-plane-mwnxm"
STEP: Collecting events for Pod kube-system/coredns-84994b8c4-h99qj
STEP: Collecting events for Pod kube-system/kube-apiserver-capz-0iy3pb-control-plane-mwnxm
STEP: Creating log watcher for controller kube-system/kube-apiserver-capz-0iy3pb-control-plane-mwnxm, container kube-apiserver
STEP: Creating log watcher for controller kube-system/kube-scheduler-capz-0iy3pb-control-plane-mwnxm, container kube-scheduler
STEP: failed to find events of Pod "kube-apiserver-capz-0iy3pb-control-plane-mwnxm"
STEP: Creating log watcher for controller kube-system/kube-controller-manager-capz-0iy3pb-control-plane-mwnxm, container kube-controller-manager
STEP: Collecting events for Pod kube-system/calico-kube-controllers-755ff8d7b5-sknlr
STEP: Creating log watcher for controller kube-system/etcd-capz-0iy3pb-control-plane-mwnxm, container etcd
STEP: Collecting events for Pod kube-system/etcd-capz-0iy3pb-control-plane-mwnxm
STEP: Creating log watcher for controller kube-system/calico-node-p9h7n, container calico-node
STEP: Creating log watcher for controller kube-system/kube-proxy-w6nhc, container kube-proxy
STEP: failed to find events of Pod "etcd-capz-0iy3pb-control-plane-mwnxm"
STEP: Collecting events for Pod kube-system/kube-proxy-w6nhc
STEP: Creating log watcher for controller kube-system/coredns-84994b8c4-cg98w, container coredns
STEP: Collecting events for Pod kube-system/coredns-84994b8c4-cg98w
STEP: Creating log watcher for controller kube-system/metrics-server-76f7667fbf-kw4l8, container metrics-server
STEP: Collecting events for Pod kube-system/metrics-server-76f7667fbf-kw4l8
STEP: Collecting events for Pod kube-system/calico-node-p9h7n
STEP: Collecting events for Pod kube-system/kube-scheduler-capz-0iy3pb-control-plane-mwnxm
STEP: failed to find events of Pod "kube-scheduler-capz-0iy3pb-control-plane-mwnxm"
STEP: Creating log watcher for controller kube-system/coredns-84994b8c4-h99qj, container coredns
STEP: Got error while iterating over activity logs for resource group capz-0iy3pb: insights.ActivityLogsClient#listNextResults: Failure responding to next results request: StatusCode=404 -- Original Error: autorest/azure: error response cannot be parsed: {"<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Strict//EN\" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd\">\r\n<html xmlns=\"http://www.w3.org/1999/xhtml\">\r\n<head>\r\n<meta http-equiv=\"Content-Type\" content=\"text/html; charset=iso-8859-1\"/>\r\n<title>404 - File or directory not found.</title>\r\n<style type=\"text/css\">\r\n<!--\r\nbody{margin:0;font-size:.7em;font-family:Verdana, Arial, Helvetica, sans-serif;background:#EEEEEE;}\r\nfieldset{padding:0 15px 10px 15px;} \r\nh1{font-size:2.4em;margin:0;color:#FFF;}\r\nh2{font-si" '\x00' '\x00'} error: invalid character '<' looking for beginning of value
STEP: Fetching activity logs took 7.763151327s
================ REDACTING LOGS ================
All sensitive variables are redacted
cluster.cluster.x-k8s.io "capz-0iy3pb" deleted
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/kind-v0.14.0 delete cluster --name=capz || true
Deleting cluster "capz" ...
... skipping 12 lines ...