This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: doc: cut v1.26.2 release
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2023-01-30 07:39
Elapsed28m0s
Revision8a6d28d337dbc82a588cb71fef2adf7185187857
Refs 1706

No Test Failures!


Error lines from build-log.txt

... skipping 807 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 129 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-z30gzj-kubeconfig; do sleep 1; done"
capz-z30gzj-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-z30gzj-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-z30gzj-control-plane-sng9b   NotReady   <none>   2s    v1.23.17-rc.0.5+a3ccd27a5da633
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'
NAME                              STATUS     ROLES                  AGE   VERSION                          INTERNAL-IP   EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION     CONTAINER-RUNTIME
capz-z30gzj-control-plane-sng9b   NotReady   control-plane,master   3s    v1.23.17-rc.0.5+a3ccd27a5da633   10.0.0.4      <none>        Ubuntu 18.04.6 LTS   5.4.0-1100-azure   containerd://1.6.15
No resources found
... skipping 10 lines ...
  Jan 30 07:53:32.055: INFO: Unable to collect logs as node doesn't have addresses
  Jan 30 07:53:32.055: INFO: Collecting logs for Windows node capz-z30gzj-md-win-jtctt in cluster capz-z30gzj in namespace default

  Jan 30 07:57:49.769: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-z30gzj-md-win-jtctt to /logs/artifacts/clusters/capz-z30gzj/machines/capz-z30gzj-md-win-865766c7b6-6vtn6/crashdumps.tar
  Jan 30 07:57:51.337: INFO: Collecting boot logs for AzureMachine capz-z30gzj-md-win-jtctt

Failed to get logs for Machine capz-z30gzj-md-win-865766c7b6-6vtn6, Cluster default/capz-z30gzj: [dialing from control plane to target node at capz-z30gzj-md-win-jtctt: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil]
  Jan 30 07:57:51.368: INFO: Unable to collect logs as node doesn't have addresses
  Jan 30 07:57:51.368: INFO: Collecting logs for Windows node capz-z30gzj-md-win-zgjv7 in cluster capz-z30gzj in namespace default

  Jan 30 08:02:13.829: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-z30gzj-md-win-zgjv7 to /logs/artifacts/clusters/capz-z30gzj/machines/capz-z30gzj-md-win-865766c7b6-qm66r/crashdumps.tar
  Jan 30 08:02:15.506: INFO: Collecting boot logs for AzureMachine capz-z30gzj-md-win-zgjv7

Failed to get logs for Machine capz-z30gzj-md-win-865766c7b6-qm66r, Cluster default/capz-z30gzj: [dialing from control plane to target node at capz-z30gzj-md-win-zgjv7: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil]
  Jan 30 08:02:15.522: INFO: Dumping workload cluster default/capz-z30gzj kube-system pod logs
  Jan 30 08:02:17.073: INFO: Creating log watcher for controller kube-system/coredns-bd6b6df9f-5pxgj, container coredns
  Jan 30 08:02:17.073: INFO: Describing Pod kube-system/coredns-bd6b6df9f-5pxgj
  Jan 30 08:02:17.300: INFO: Creating log watcher for controller kube-system/coredns-bd6b6df9f-cj55k, container coredns
  Jan 30 08:02:17.300: INFO: Describing Pod kube-system/coredns-bd6b6df9f-cj55k
  Jan 30 08:02:17.521: INFO: Creating log watcher for controller kube-system/etcd-capz-z30gzj-control-plane-sng9b, container etcd
... skipping 31 lines ...