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-30 05:12
Elapsed	32m4s
Revision	811840a4df93d2694ed7545ed50a580b66eaa102
Refs	1699

• artifacts
• build log

No Test Failures!

---

Error lines from build-log.txt

• Expand Skipped Lines
• Raw build-log.txt

... skipping 806 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 153 lines ...
  Jan 30 05:28:12.373: INFO: Unable to collect logs as node doesn't have addresses
  Jan 30 05:28:12.373: INFO: Collecting logs for Windows node capz-xpejc4-md-win-drr56 in cluster capz-xpejc4 in namespace default

  Jan 30 05:32:28.892: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-xpejc4-md-win-drr56 to /logs/artifacts/clusters/capz-xpejc4/machines/capz-xpejc4-md-win-577bb4d456-65qbx/crashdumps.tar
  Jan 30 05:32:29.940: INFO: Collecting boot logs for AzureMachine capz-xpejc4-md-win-drr56

Failed to get logs for Machine capz-xpejc4-md-win-577bb4d456-65qbx, Cluster default/capz-xpejc4: [dialing from control plane to target node at capz-xpejc4-md-win-drr56: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil]
  Jan 30 05:32:29.962: INFO: Unable to collect logs as node doesn't have addresses
  Jan 30 05:32:29.962: INFO: Collecting logs for Windows node capz-xpejc4-md-win-h4kzb in cluster capz-xpejc4 in namespace default

  Jan 30 05:36:43.228: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-xpejc4-md-win-h4kzb to /logs/artifacts/clusters/capz-xpejc4/machines/capz-xpejc4-md-win-577bb4d456-fjkwh/crashdumps.tar
  Jan 30 05:36:44.549: INFO: Collecting boot logs for AzureMachine capz-xpejc4-md-win-h4kzb

Failed to get logs for Machine capz-xpejc4-md-win-577bb4d456-fjkwh, Cluster default/capz-xpejc4: dialing from control plane to target node at capz-xpejc4-md-win-h4kzb: ssh: rejected: connect failed (Temporary failure in name resolution)
  Jan 30 05:36:45.649: INFO: Dumping workload cluster default/capz-xpejc4 kube-system pod logs
  Jan 30 05:36:46.150: INFO: Creating log watcher for controller kube-system/containerd-logger-4cbvq, container containerd-logger
  Jan 30 05:36:46.150: INFO: Describing Pod kube-system/containerd-logger-4cbvq
  Jan 30 05:36:46.214: INFO: Creating log watcher for controller kube-system/containerd-logger-xlrtk, container containerd-logger
  Jan 30 05:36:46.214: INFO: Describing Pod kube-system/containerd-logger-xlrtk
  Jan 30 05:36:46.273: INFO: Creating log watcher for controller kube-system/coredns-bd6b6df9f-gkrm2, container coredns
... skipping 39 lines ...