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 05:46
Elapsed	37m10s
Revision	6944e57066228ac2ead79868cabed9da29588cca
Refs	1169

• artifacts
• build log

No Test Failures!

---

Error lines from build-log.txt

• Expand Skipped Lines
• Raw build-log.txt

... skipping 787 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 157 lines ...
  Jan 26 06:06:06.543: INFO: Unable to collect logs as node doesn't have addresses
  Jan 26 06:06:06.543: INFO: Collecting logs for Windows node capz-x6242s-md-win-sxn7z in cluster capz-x6242s in namespace default

  Jan 26 06:10:27.955: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-x6242s-md-win-sxn7z to /logs/artifacts/clusters/capz-x6242s/machines/capz-x6242s-md-win-68dcb9c58f-c4gvz/crashdumps.tar
  Jan 26 06:10:29.572: INFO: Collecting boot logs for AzureMachine capz-x6242s-md-win-sxn7z

Failed to get logs for Machine capz-x6242s-md-win-68dcb9c58f-c4gvz, Cluster default/capz-x6242s: [dialing from control plane to target node at capz-x6242s-md-win-sxn7z: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil]
  Jan 26 06:10:29.604: INFO: Unable to collect logs as node doesn't have addresses
  Jan 26 06:10:29.604: INFO: Collecting logs for Windows node capz-x6242s-md-win-5w9hj in cluster capz-x6242s in namespace default

  Jan 26 06:14:51.352: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-x6242s-md-win-5w9hj to /logs/artifacts/clusters/capz-x6242s/machines/capz-x6242s-md-win-68dcb9c58f-tdp8x/crashdumps.tar
  Jan 26 06:14:53.059: INFO: Collecting boot logs for AzureMachine capz-x6242s-md-win-5w9hj

Failed to get logs for Machine capz-x6242s-md-win-68dcb9c58f-tdp8x, Cluster default/capz-x6242s: [dialing from control plane to target node at capz-x6242s-md-win-5w9hj: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil]
  Jan 26 06:14:53.079: INFO: Dumping workload cluster default/capz-x6242s kube-system pod logs
  Jan 26 06:14:54.604: INFO: Fetching kube-system pod logs took 1.525051707s
  Jan 26 06:14:54.604: INFO: Dumping workload cluster default/capz-x6242s Azure activity log
  Jan 26 06:14:54.604: INFO: Collecting events for Pod kube-system/coredns-bd6b6df9f-s6zld
  Jan 26 06:14:54.604: INFO: Collecting events for Pod kube-system/kube-proxy-dgqgf
  Jan 26 06:14:54.604: INFO: Creating log watcher for controller kube-system/kube-controller-manager-capz-x6242s-control-plane-2qgd7, container kube-controller-manager
... skipping 39 lines ...