This job view page is being replaced by Spyglass soon. Check out the new job view.

PR	andyzhangx: fix: panic when allow-empty-cloud-config is set
Result	FAILURE
Tests	0 failed / 0 succeeded
Started	2023-01-29 08:16
Elapsed	30m43s
Revision	811840a4df93d2694ed7545ed50a580b66eaa102
Refs	1699

• artifacts
• build log

No Test Failures!

---

Error lines from build-log.txt

• Expand Skipped Lines
• Raw build-log.txt

... skipping 804 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 155 lines ...
  Jan 29 08:32:47.831: INFO: Unable to collect logs as node doesn't have addresses
  Jan 29 08:32:47.831: INFO: Collecting logs for Windows node capz-xagw9y-md-win-qvrwd in cluster capz-xagw9y in namespace default

  Jan 29 08:37:07.434: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-xagw9y-md-win-qvrwd to /logs/artifacts/clusters/capz-xagw9y/machines/capz-xagw9y-md-win-9dbb88d77-2dvl9/crashdumps.tar
  Jan 29 08:37:08.567: INFO: Collecting boot logs for AzureMachine capz-xagw9y-md-win-qvrwd

Failed to get logs for Machine capz-xagw9y-md-win-9dbb88d77-2dvl9, Cluster default/capz-xagw9y: [dialing from control plane to target node at capz-xagw9y-md-win-qvrwd: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil]
  Jan 29 08:37:08.720: INFO: Unable to collect logs as node doesn't have addresses
  Jan 29 08:37:08.720: INFO: Collecting logs for Windows node capz-xagw9y-md-win-tk5x4 in cluster capz-xagw9y in namespace default

  Jan 29 08:41:22.271: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-xagw9y-md-win-tk5x4 to /logs/artifacts/clusters/capz-xagw9y/machines/capz-xagw9y-md-win-9dbb88d77-tmdmk/crashdumps.tar
  Jan 29 08:41:23.538: INFO: Collecting boot logs for AzureMachine capz-xagw9y-md-win-tk5x4

Failed to get logs for Machine capz-xagw9y-md-win-9dbb88d77-tmdmk, Cluster default/capz-xagw9y: [dialing from control plane to target node at capz-xagw9y-md-win-tk5x4: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil]
  Jan 29 08:41:23.578: INFO: Dumping workload cluster default/capz-xagw9y kube-system pod logs
  Jan 29 08:41:24.537: INFO: Creating log watcher for controller kube-system/coredns-bd6b6df9f-9lwgr, container coredns
  Jan 29 08:41:24.537: INFO: Describing Pod kube-system/coredns-bd6b6df9f-9lwgr
  Jan 29 08:41:24.672: INFO: Creating log watcher for controller kube-system/coredns-bd6b6df9f-ns6hf, container coredns
  Jan 29 08:41:24.674: INFO: Describing Pod kube-system/coredns-bd6b6df9f-ns6hf
  Jan 29 08:41:24.805: INFO: Creating log watcher for controller kube-system/etcd-capz-xagw9y-control-plane-nxfz9, container etcd
... skipping 31 lines ...