This job view page is being replaced by Spyglass soon. Check out the new job view.
PRandyzhangx: fix: panic when allow-empty-cloud-config is set
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2023-01-29 12:26
Elapsed27m56s
Revision811840a4df93d2694ed7545ed50a580b66eaa102
Refs 1699

No Test Failures!


Error lines from build-log.txt

... skipping 805 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 156 lines ...
  Jan 29 12:39:58.807: INFO: Unable to collect logs as node doesn't have addresses
  Jan 29 12:39:58.807: INFO: Collecting logs for Windows node capz-9i7ylm-md-win-lbw52 in cluster capz-9i7ylm in namespace default

  Jan 29 12:44:24.988: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-9i7ylm-md-win-lbw52 to /logs/artifacts/clusters/capz-9i7ylm/machines/capz-9i7ylm-md-win-8698bdcb8c-hnjqx/crashdumps.tar
  Jan 29 12:44:26.582: INFO: Collecting boot logs for AzureMachine capz-9i7ylm-md-win-lbw52

Failed to get logs for Machine capz-9i7ylm-md-win-8698bdcb8c-hnjqx, Cluster default/capz-9i7ylm: [dialing from control plane to target node at capz-9i7ylm-md-win-lbw52: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil]
  Jan 29 12:44:26.604: INFO: Unable to collect logs as node doesn't have addresses
  Jan 29 12:44:26.604: INFO: Collecting logs for Windows node capz-9i7ylm-md-win-sm9gh in cluster capz-9i7ylm in namespace default

  Jan 29 12:48:50.057: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-9i7ylm-md-win-sm9gh to /logs/artifacts/clusters/capz-9i7ylm/machines/capz-9i7ylm-md-win-8698bdcb8c-qfgm7/crashdumps.tar
  Jan 29 12:48:51.804: INFO: Collecting boot logs for AzureMachine capz-9i7ylm-md-win-sm9gh

Failed to get logs for Machine capz-9i7ylm-md-win-8698bdcb8c-qfgm7, Cluster default/capz-9i7ylm: dialing from control plane to target node at capz-9i7ylm-md-win-sm9gh: ssh: rejected: connect failed (Temporary failure in name resolution)
  Jan 29 12:48:53.392: INFO: Dumping workload cluster default/capz-9i7ylm kube-system pod logs
  Jan 29 12:48:54.880: INFO: Creating log watcher for controller kube-system/containerd-logger-dzqff, container containerd-logger
  Jan 29 12:48:54.881: INFO: Describing Pod kube-system/containerd-logger-dzqff
  Jan 29 12:48:55.091: INFO: Creating log watcher for controller kube-system/containerd-logger-vd6fc, container containerd-logger
  Jan 29 12:48:55.091: INFO: Describing Pod kube-system/containerd-logger-vd6fc
  Jan 29 12:48:55.300: INFO: Creating log watcher for controller kube-system/coredns-bd6b6df9f-fqh9r, container coredns
... skipping 39 lines ...