This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2022-07-07 19:46
Elapsed50m48s
Revisionrelease-1.3

No Test Failures!


Error lines from build-log.txt

... skipping 623 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
# Deploy CAPI
curl --retry 3 -sSL https://github.com/kubernetes-sigs/cluster-api/releases/download/v1.1.4/cluster-api-components.yaml | /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/hack/tools/bin/envsubst-v2.0.0-20210730161058-179042472c46 | kubectl apply -f -
namespace/capi-system created
customresourcedefinition.apiextensions.k8s.io/clusterclasses.cluster.x-k8s.io created
... skipping 160 lines ...
INFO: Creating log watcher for controller capz-system/capz-controller-manager, pod capz-controller-manager-67454cb5-lnv4x, container manager
STEP: Dumping workload cluster default/capz-psjl9e logs
Jul  7 20:29:38.506: INFO: Collecting logs for Linux node capz-psjl9e-control-plane-c6vvw in cluster capz-psjl9e in namespace default

Jul  7 20:30:38.507: INFO: Collecting boot logs for AzureMachine capz-psjl9e-control-plane-c6vvw

Failed to get logs for machine capz-psjl9e-control-plane-xn6tq, cluster default/capz-psjl9e: open /etc/azure-ssh/azure-ssh: no such file or directory
Jul  7 20:30:39.266: INFO: Collecting logs for Linux node capz-psjl9e-md-0-g7c5n in cluster capz-psjl9e in namespace default

Jul  7 20:31:39.268: INFO: Collecting boot logs for AzureMachine capz-psjl9e-md-0-g7c5n

Failed to get logs for machine capz-psjl9e-md-0-5d59cc9557-frhv2, cluster default/capz-psjl9e: [open /etc/azure-ssh/azure-ssh: no such file or directory, Unable to collect VM Boot Diagnostic logs: failed to get boot diagnostics data: compute.VirtualMachinesClient#RetrieveBootDiagnosticsData: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="ResourceNotFound" Message="The Resource 'Microsoft.Compute/virtualMachines/capz-psjl9e-md-0-g7c5n' under resource group 'capz-psjl9e' was not found. For more details please go to https://aka.ms/ARMResourceNotFoundFix"]
Failed to get logs for machine capz-psjl9e-md-0-5d59cc9557-gg246, cluster default/capz-psjl9e: azuremachines.infrastructure.cluster.x-k8s.io "capz-psjl9e-md-0-jfnvc" not found
STEP: Dumping workload cluster default/capz-psjl9e kube-system pod logs
STEP: Fetching kube-system pod logs took 409.549993ms
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-hh858, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/metrics-server-8c95fb79b-ld6fl
STEP: Collecting events for Pod kube-system/etcd-capz-psjl9e-control-plane-c6vvw
STEP: Creating log watcher for controller kube-system/kube-proxy-fbhgz, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-scheduler-capz-psjl9e-control-plane-c6vvw, container kube-scheduler
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-7zk9s, container coredns
STEP: failed to find events of Pod "etcd-capz-psjl9e-control-plane-c6vvw"
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-7zk9s
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-s286x, container coredns
STEP: Collecting events for Pod kube-system/kube-proxy-fbhgz
STEP: Creating log watcher for controller kube-system/calico-node-88bg9, container calico-node
STEP: Collecting events for Pod kube-system/calico-node-88bg9
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-hh858
STEP: Collecting events for Pod kube-system/kube-scheduler-capz-psjl9e-control-plane-c6vvw
STEP: failed to find events of Pod "kube-scheduler-capz-psjl9e-control-plane-c6vvw"
STEP: Collecting events for Pod kube-system/kube-apiserver-capz-psjl9e-control-plane-c6vvw
STEP: failed to find events of Pod "kube-apiserver-capz-psjl9e-control-plane-c6vvw"
STEP: Creating log watcher for controller kube-system/kube-apiserver-capz-psjl9e-control-plane-c6vvw, container kube-apiserver
STEP: Dumping workload cluster default/capz-psjl9e Azure activity log
STEP: Creating log watcher for controller kube-system/metrics-server-8c95fb79b-ld6fl, container metrics-server
STEP: Creating log watcher for controller kube-system/kube-controller-manager-capz-psjl9e-control-plane-c6vvw, container kube-controller-manager
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-s286x
STEP: Creating log watcher for controller kube-system/etcd-capz-psjl9e-control-plane-c6vvw, container etcd
STEP: Collecting events for Pod kube-system/kube-controller-manager-capz-psjl9e-control-plane-c6vvw
STEP: failed to find events of Pod "kube-controller-manager-capz-psjl9e-control-plane-c6vvw"
STEP: Fetching activity logs took 4.421349611s
================ REDACTING LOGS ================
All sensitive variables are redacted
cluster.cluster.x-k8s.io "capz-psjl9e" deleted
kind delete cluster --name=capz || true
Deleting cluster "capz" ...
... skipping 12 lines ...