This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2022-09-01 20:10
Elapsed53m36s
Revisionrelease-1.4

No Test Failures!


Error lines from build-log.txt

... skipping 628 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 165 lines ...
INFO: Creating log watcher for controller capz-system/capz-controller-manager, pod capz-controller-manager-858df9cd95-6lh62, container manager
STEP: Dumping workload cluster default/capz-ybe7ly logs
Sep  1 20:55:02.878: INFO: Collecting logs for Linux node capz-ybe7ly-control-plane-ps49d in cluster capz-ybe7ly in namespace default

Sep  1 20:56:02.880: INFO: Collecting boot logs for AzureMachine capz-ybe7ly-control-plane-ps49d

Failed to get logs for machine capz-ybe7ly-control-plane-57sbr, cluster default/capz-ybe7ly: open /etc/azure-ssh/azure-ssh: no such file or directory
Sep  1 20:56:04.120: INFO: Collecting logs for Linux node capz-ybe7ly-md-0-xd98n in cluster capz-ybe7ly in namespace default

Sep  1 20:57:04.122: INFO: Collecting boot logs for AzureMachine capz-ybe7ly-md-0-xd98n

Failed to get logs for machine capz-ybe7ly-md-0-5b5c4546dd-7bpkh, cluster default/capz-ybe7ly: [open /etc/azure-ssh/azure-ssh: no such file or directory, Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil]
Sep  1 20:57:04.148: INFO: Collecting logs for Linux node capz-ybe7ly-md-0-hft6h in cluster capz-ybe7ly in namespace default

Sep  1 20:58:04.150: INFO: Collecting boot logs for AzureMachine capz-ybe7ly-md-0-hft6h

Failed to get logs for machine capz-ybe7ly-md-0-5b5c4546dd-pwlxf, cluster default/capz-ybe7ly: [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-ybe7ly kube-system pod logs
STEP: Creating log watcher for controller kube-system/calico-node-qkrr9, container calico-node
STEP: Collecting events for Pod kube-system/etcd-capz-ybe7ly-control-plane-ps49d
STEP: Creating log watcher for controller kube-system/kube-apiserver-capz-ybe7ly-control-plane-ps49d, container kube-apiserver
STEP: Fetching kube-system pod logs took 1.077914153s
STEP: Dumping workload cluster default/capz-ybe7ly Azure activity log
STEP: Collecting events for Pod kube-system/metrics-server-8c95fb79b-cchg7
STEP: Collecting events for Pod kube-system/kube-proxy-5b52w
STEP: Creating log watcher for controller kube-system/kube-scheduler-capz-ybe7ly-control-plane-ps49d, container kube-scheduler
STEP: Collecting events for Pod kube-system/kube-scheduler-capz-ybe7ly-control-plane-ps49d
STEP: failed to find events of Pod "kube-scheduler-capz-ybe7ly-control-plane-ps49d"
STEP: Creating log watcher for controller kube-system/metrics-server-8c95fb79b-cchg7, container metrics-server
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-zgbpl, container coredns
STEP: Collecting events for Pod kube-system/calico-node-qkrr9
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-fqq52, container coredns
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-fqq52
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-pv96w, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-pv96w
STEP: Creating log watcher for controller kube-system/kube-controller-manager-capz-ybe7ly-control-plane-ps49d, container kube-controller-manager
STEP: Collecting events for Pod kube-system/kube-apiserver-capz-ybe7ly-control-plane-ps49d
STEP: Collecting events for Pod kube-system/kube-controller-manager-capz-ybe7ly-control-plane-ps49d
STEP: failed to find events of Pod "kube-controller-manager-capz-ybe7ly-control-plane-ps49d"
STEP: Creating log watcher for controller kube-system/kube-proxy-5b52w, container kube-proxy
STEP: Creating log watcher for controller kube-system/etcd-capz-ybe7ly-control-plane-ps49d, container etcd
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-zgbpl
STEP: failed to find events of Pod "etcd-capz-ybe7ly-control-plane-ps49d"
STEP: Got error while iterating over activity logs for resource group capz-ybe7ly: 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 6.529427873s
================ REDACTING LOGS ================
All sensitive variables are redacted
cluster.cluster.x-k8s.io "capz-ybe7ly" 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 ...