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

PR	andyzhangx: fix: remove python in container image to fix CVE
Result	FAILURE
Tests	0 failed / 0 succeeded
Started	2023-01-26 07:31
Elapsed	29m6s
Revision	6944e57066228ac2ead79868cabed9da29588cca
Refs	1169

• artifacts
• build log

No Test Failures!

---

Error lines from build-log.txt

• Expand Skipped Lines
• Raw build-log.txt

... skipping 786 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 158 lines ...
  Jan 26 07:46:21.216: INFO: Unable to collect logs as node doesn't have addresses
  Jan 26 07:46:21.217: INFO: Collecting logs for Windows node capz-b1g9nf-md-win-jlgp7 in cluster capz-b1g9nf in namespace default

  Jan 26 07:50:37.167: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-b1g9nf-md-win-jlgp7 to /logs/artifacts/clusters/capz-b1g9nf/machines/capz-b1g9nf-md-win-6b7c567c87-ntdjs/crashdumps.tar
  Jan 26 07:50:38.315: INFO: Collecting boot logs for AzureMachine capz-b1g9nf-md-win-jlgp7

Failed to get logs for Machine capz-b1g9nf-md-win-6b7c567c87-ntdjs, Cluster default/capz-b1g9nf: [dialing from control plane to target node at capz-b1g9nf-md-win-jlgp7: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil]
  Jan 26 07:50:38.344: INFO: Unable to collect logs as node doesn't have addresses
  Jan 26 07:50:38.344: INFO: Collecting logs for Windows node capz-b1g9nf-md-win-2zn47 in cluster capz-b1g9nf in namespace default

  Jan 26 07:54:54.888: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-b1g9nf-md-win-2zn47 to /logs/artifacts/clusters/capz-b1g9nf/machines/capz-b1g9nf-md-win-6b7c567c87-p9f7h/crashdumps.tar
  Jan 26 07:54:56.156: INFO: Collecting boot logs for AzureMachine capz-b1g9nf-md-win-2zn47

Failed to get logs for Machine capz-b1g9nf-md-win-6b7c567c87-p9f7h, Cluster default/capz-b1g9nf: [dialing from control plane to target node at capz-b1g9nf-md-win-2zn47: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil]
  Jan 26 07:54:56.182: INFO: Dumping workload cluster default/capz-b1g9nf kube-system pod logs
  Jan 26 07:54:57.067: INFO: Collecting events for Pod kube-system/coredns-bd6b6df9f-2msd8
  Jan 26 07:54:57.067: INFO: Creating log watcher for controller kube-system/etcd-capz-b1g9nf-control-plane-kknph, container etcd
  Jan 26 07:54:57.067: INFO: Creating log watcher for controller kube-system/coredns-bd6b6df9f-cbj2n, container coredns
  Jan 26 07:54:57.067: INFO: Collecting events for Pod kube-system/etcd-capz-b1g9nf-control-plane-kknph
  Jan 26 07:54:57.067: INFO: Fetching kube-system pod logs took 884.962406ms
... skipping 31 lines ...