periodic-cluster-api-provider-azure-capi-e2e-v1beta1 #1607844369174368256
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 6 succeeded |
| Started | |
| Elapsed | 4h15m |
| Revision | release-1.6 |
capz-e2e Running the Cluster API E2E tests Running the self-hosted spec Should pivot the bootstrap cluster to a self-hosted cluster
capz-e2e Running the Cluster API E2E tests Should successfully exercise machine pools Should successfully create a cluster with machine pool machines
capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger KCP remediation
capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger machine deployment remediation
capz-e2e Running the Cluster API E2E tests Should successfully scale out and scale in a MachineDeployment Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count
capz-e2e Running the Cluster API E2E tests Should successfully set and use node drain timeout A node should be forcefully removed if it cannot be drained in time
capz-e2e Running the Cluster API E2E tests API Version Upgrade upgrade from v1alpha4 to v1beta1, and scale workload clusters created in v1alpha4 Should create a management cluster and then upgrade all the providers
capz-e2e Running the Cluster API E2E tests Running KCP upgrade in a HA cluster [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e Running the Cluster API E2E tests Running KCP upgrade in a HA cluster using scale in rollout [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e Running the Cluster API E2E tests Running the workload cluster upgrade spec [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
... skipping 540 lines ... [1mShould pivot the bootstrap cluster to a self-hosted cluster[0m [37m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_selfhosted.go:107[0m INFO: "Should pivot the bootstrap cluster to a self-hosted cluster" started at Tue, 27 Dec 2022 21:10:47 UTC on Ginkgo node 9 of 10 [1mSTEP[0m: Creating namespace "self-hosted" for hosting the cluster Dec 27 21:10:47.623: INFO: starting to create namespace for hosting the "self-hosted" test spec 2022/12/27 21:10:47 failed trying to get namespace (self-hosted):namespaces "self-hosted" not found INFO: Creating namespace self-hosted INFO: Creating event watcher for namespace "self-hosted" [1mSTEP[0m: Creating a workload cluster INFO: Creating the workload cluster with name "self-hosted-zk82m1" using the "management" template (Kubernetes v1.23.15, 1 control-plane machines, 1 worker machines) INFO: Getting the cluster template yaml INFO: clusterctl config cluster self-hosted-zk82m1 --infrastructure (default) --kubernetes-version v1.23.15 --control-plane-machine-count 1 --worker-machine-count 1 --flavor management ... skipping 67 lines ... [1mSTEP[0m: Creating log watcher for controller kube-system/kube-scheduler-self-hosted-zk82m1-control-plane-kmxzp, container kube-scheduler [1mSTEP[0m: Collecting events for Pod kube-system/coredns-bd6b6df9f-ctxt9 [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-qcxkb, container kube-proxy [1mSTEP[0m: Collecting events for Pod kube-system/kube-scheduler-self-hosted-zk82m1-control-plane-kmxzp [1mSTEP[0m: Collecting events for Pod kube-system/calico-node-sdvt2 [1mSTEP[0m: Creating log watcher for controller kube-system/coredns-bd6b6df9f-6k5r7, container coredns [1mSTEP[0m: failed to find events of Pod "kube-scheduler-self-hosted-zk82m1-control-plane-kmxzp" [1mSTEP[0m: Creating log watcher for controller kube-system/etcd-self-hosted-zk82m1-control-plane-kmxzp, container etcd [1mSTEP[0m: Creating log watcher for controller kube-system/coredns-bd6b6df9f-ctxt9, container coredns [1mSTEP[0m: Dumping workload cluster self-hosted/self-hosted-zk82m1 Azure activity log [1mSTEP[0m: Creating log watcher for controller kube-system/calico-kube-controllers-85f479877b-tcbrs, container calico-kube-controllers [1mSTEP[0m: Collecting events for Pod kube-system/calico-kube-controllers-85f479877b-tcbrs [1mSTEP[0m: Collecting events for Pod kube-system/etcd-self-hosted-zk82m1-control-plane-kmxzp [1mSTEP[0m: failed to find events of Pod "etcd-self-hosted-zk82m1-control-plane-kmxzp" [1mSTEP[0m: Collecting events for Pod kube-system/calico-node-j4vbz [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-j4vbz, container calico-node [1mSTEP[0m: Creating log watcher for controller kube-system/kube-apiserver-self-hosted-zk82m1-control-plane-kmxzp, container kube-apiserver [1mSTEP[0m: Collecting events for Pod kube-system/kube-apiserver-self-hosted-zk82m1-control-plane-kmxzp [1mSTEP[0m: failed to find events of Pod "kube-apiserver-self-hosted-zk82m1-control-plane-kmxzp" [1mSTEP[0m: Creating log watcher for controller kube-system/kube-controller-manager-self-hosted-zk82m1-control-plane-kmxzp, container kube-controller-manager [1mSTEP[0m: Collecting events for Pod kube-system/kube-controller-manager-self-hosted-zk82m1-control-plane-kmxzp [1mSTEP[0m: failed to find events of Pod "kube-controller-manager-self-hosted-zk82m1-control-plane-kmxzp" [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-gcf27, container kube-proxy [1mSTEP[0m: Fetching activity logs took 2.02741533s Dec 27 21:19:31.369: INFO: Dumping all the Cluster API resources in the "self-hosted" namespace Dec 27 21:19:31.674: INFO: Deleting all clusters in the self-hosted namespace [1mSTEP[0m: Deleting cluster self-hosted-zk82m1 INFO: Waiting for the Cluster self-hosted/self-hosted-zk82m1 to be deleted [1mSTEP[0m: Waiting for cluster self-hosted-zk82m1 to be deleted INFO: Got error while streaming logs for pod capz-system/capz-controller-manager-74977fb6fc-96skq, container manager: http2: client connection lost INFO: Got error while streaming logs for pod capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager-8f6f78b8b-lhngh, container manager: http2: client connection lost INFO: Got error while streaming logs for pod capi-system/capi-controller-manager-5b6d47468d-xxtz2, container manager: http2: client connection lost INFO: Got error while streaming logs for pod capi-kubeadm-control-plane-system/capi-kubeadm-control-plane-controller-manager-66968bb4c5-gz28j, container manager: http2: client connection lost Dec 27 21:24:11.842: INFO: Deleting namespace used for hosting the "self-hosted" test spec INFO: Deleting namespace self-hosted Dec 27 21:24:11.863: INFO: Checking if any resources are left over in Azure for spec "self-hosted" [1mSTEP[0m: Redacting sensitive information from logs Dec 27 21:24:42.433: INFO: Cleaning up after "Running the Cluster API E2E tests Running the self-hosted spec Should pivot the bootstrap cluster to a self-hosted cluster" spec [1mSTEP[0m: Redacting sensitive information from logs ... skipping 73 lines ... [1mSTEP[0m: Collecting events for Pod kube-system/coredns-bd6b6df9f-x28gb [1mSTEP[0m: Creating log watcher for controller kube-system/etcd-mhc-remediation-fslbf8-control-plane-4fw72, container etcd [1mSTEP[0m: Collecting events for Pod kube-system/etcd-mhc-remediation-fslbf8-control-plane-4fw72 [1mSTEP[0m: Creating log watcher for controller kube-system/kube-apiserver-mhc-remediation-fslbf8-control-plane-4fw72, container kube-apiserver [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-x9qzm, container calico-node [1mSTEP[0m: Collecting events for Pod kube-system/kube-apiserver-mhc-remediation-fslbf8-control-plane-4fw72 [1mSTEP[0m: failed to find events of Pod "kube-apiserver-mhc-remediation-fslbf8-control-plane-4fw72" [1mSTEP[0m: Creating log watcher for controller kube-system/coredns-bd6b6df9f-6rtqm, container coredns [1mSTEP[0m: failed to find events of Pod "etcd-mhc-remediation-fslbf8-control-plane-4fw72" [1mSTEP[0m: Creating log watcher for controller kube-system/coredns-bd6b6df9f-x28gb, container coredns [1mSTEP[0m: Creating log watcher for controller kube-system/kube-controller-manager-mhc-remediation-fslbf8-control-plane-4fw72, container kube-controller-manager [1mSTEP[0m: Collecting events for Pod kube-system/calico-kube-controllers-85f479877b-cjtw2 [1mSTEP[0m: Collecting events for Pod kube-system/kube-controller-manager-mhc-remediation-fslbf8-control-plane-4fw72 [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-b4cfk, container kube-proxy [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-b4cfk [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-6kk4j, container kube-proxy [1mSTEP[0m: Creating log watcher for controller kube-system/kube-scheduler-mhc-remediation-fslbf8-control-plane-4fw72, container kube-scheduler [1mSTEP[0m: Collecting events for Pod kube-system/coredns-bd6b6df9f-6rtqm [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-6kk4j [1mSTEP[0m: Collecting events for Pod kube-system/kube-scheduler-mhc-remediation-fslbf8-control-plane-4fw72 [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-w2djh, container calico-node [1mSTEP[0m: failed to find events of Pod "kube-controller-manager-mhc-remediation-fslbf8-control-plane-4fw72" [1mSTEP[0m: failed to find events of Pod "kube-scheduler-mhc-remediation-fslbf8-control-plane-4fw72" [1mSTEP[0m: Fetching activity logs took 1.506635643s [1mSTEP[0m: Dumping all the Cluster API resources in the "mhc-remediation-ajlbf4" namespace [1mSTEP[0m: Deleting cluster mhc-remediation-ajlbf4/mhc-remediation-fslbf8 [1mSTEP[0m: Deleting cluster mhc-remediation-fslbf8 INFO: Waiting for the Cluster mhc-remediation-ajlbf4/mhc-remediation-fslbf8 to be deleted [1mSTEP[0m: Waiting for cluster mhc-remediation-fslbf8 to be deleted ... skipping 208 lines ... Dec 27 21:19:21.716: INFO: Collecting logs for Windows node quick-sta-9chxc in cluster quick-start-icou2q in namespace quick-start-43pb44 Dec 27 21:22:02.050: INFO: Attempting to copy file /c:/crashdumps.tar on node quick-sta-9chxc to /logs/artifacts/clusters/quick-start-icou2q/machines/quick-start-icou2q-md-win-cc4d74654-fb6lf/crashdumps.tar Dec 27 21:22:04.146: INFO: Collecting boot logs for AzureMachine quick-start-icou2q-md-win-9chxc Failed to get logs for machine quick-start-icou2q-md-win-cc4d74654-fb6lf, cluster quick-start-43pb44/quick-start-icou2q: [running command "Get-Content "C:\\cni.log"": Process exited with status 1, running command "$p = 'c:\localdumps' ; if (Test-Path $p) { tar.exe -cvzf c:\crashdumps.tar $p *>&1 | %{ Write-Output "$_"} } else { Write-Host "No crash dumps found at $p" }": Process exited with status 1] Dec 27 21:22:04.989: INFO: Collecting logs for Windows node quick-sta-7g9rp in cluster quick-start-icou2q in namespace quick-start-43pb44 Dec 27 21:24:47.077: INFO: Attempting to copy file /c:/crashdumps.tar on node quick-sta-7g9rp to /logs/artifacts/clusters/quick-start-icou2q/machines/quick-start-icou2q-md-win-cc4d74654-hmlrv/crashdumps.tar Dec 27 21:24:49.028: INFO: Collecting boot logs for AzureMachine quick-start-icou2q-md-win-7g9rp Failed to get logs for machine quick-start-icou2q-md-win-cc4d74654-hmlrv, cluster quick-start-43pb44/quick-start-icou2q: [running command "Get-Content "C:\\cni.log"": Process exited with status 1, running command "$p = 'c:\localdumps' ; if (Test-Path $p) { tar.exe -cvzf c:\crashdumps.tar $p *>&1 | %{ Write-Output "$_"} } else { Write-Host "No crash dumps found at $p" }": Process exited with status 1] [1mSTEP[0m: Dumping workload cluster quick-start-43pb44/quick-start-icou2q kube-system pod logs [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-ds756, container calico-node [1mSTEP[0m: Fetching kube-system pod logs took 480.73051ms [1mSTEP[0m: Dumping workload cluster quick-start-43pb44/quick-start-icou2q Azure activity log [1mSTEP[0m: Collecting events for Pod kube-system/calico-node-ds756 [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-windows-bsv62, container calico-node-startup ... skipping 17 lines ... [1mSTEP[0m: Collecting events for Pod kube-system/csi-proxy-l2xkr [1mSTEP[0m: Creating log watcher for controller kube-system/csi-proxy-n6t9b, container csi-proxy [1mSTEP[0m: Collecting events for Pod kube-system/calico-node-4k8gj [1mSTEP[0m: Creating log watcher for controller kube-system/coredns-bd6b6df9f-x6d57, container coredns [1mSTEP[0m: Creating log watcher for controller kube-system/csi-proxy-l2xkr, container csi-proxy [1mSTEP[0m: Collecting events for Pod kube-system/etcd-quick-start-icou2q-control-plane-gf4jb [1mSTEP[0m: failed to find events of Pod "etcd-quick-start-icou2q-control-plane-gf4jb" [1mSTEP[0m: Creating log watcher for controller kube-system/kube-apiserver-quick-start-icou2q-control-plane-gf4jb, container kube-apiserver [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-mj4vc [1mSTEP[0m: Collecting events for Pod kube-system/kube-apiserver-quick-start-icou2q-control-plane-gf4jb [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-windows-wbfs5, container kube-proxy [1mSTEP[0m: Collecting events for Pod kube-system/kube-scheduler-quick-start-icou2q-control-plane-gf4jb [1mSTEP[0m: failed to find events of Pod "kube-apiserver-quick-start-icou2q-control-plane-gf4jb" [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-windows-szr4n, container kube-proxy [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-7b98q, container kube-proxy [1mSTEP[0m: failed to find events of Pod "kube-scheduler-quick-start-icou2q-control-plane-gf4jb" [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-windows-szr4n [1mSTEP[0m: Creating log watcher for controller kube-system/kube-scheduler-quick-start-icou2q-control-plane-gf4jb, container kube-scheduler [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-7b98q [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-mj4vc, container kube-proxy [1mSTEP[0m: Creating log watcher for controller kube-system/kube-controller-manager-quick-start-icou2q-control-plane-gf4jb, container kube-controller-manager [1mSTEP[0m: Collecting events for Pod kube-system/kube-controller-manager-quick-start-icou2q-control-plane-gf4jb ... skipping 107 lines ... [1mSTEP[0m: Creating log watcher for controller kube-system/etcd-node-drain-95zgpm-control-plane-cmjnk, container etcd [1mSTEP[0m: Fetching kube-system pod logs took 406.486698ms [1mSTEP[0m: Dumping workload cluster node-drain-7yhoyy/node-drain-95zgpm Azure activity log [1mSTEP[0m: Collecting events for Pod kube-system/kube-controller-manager-node-drain-95zgpm-control-plane-5cqp6 [1mSTEP[0m: Collecting events for Pod kube-system/kube-apiserver-node-drain-95zgpm-control-plane-cmjnk [1mSTEP[0m: Collecting events for Pod kube-system/coredns-bd6b6df9f-sjh85 [1mSTEP[0m: Error starting logs stream for pod kube-system/kube-controller-manager-node-drain-95zgpm-control-plane-5cqp6, container kube-controller-manager: pods "node-drain-95zgpm-control-plane-5cqp6" not found [1mSTEP[0m: Error starting logs stream for pod kube-system/calico-node-dbjts, container calico-node: pods "node-drain-95zgpm-control-plane-5cqp6" not found [1mSTEP[0m: Error starting logs stream for pod kube-system/kube-apiserver-node-drain-95zgpm-control-plane-5cqp6, container kube-apiserver: pods "node-drain-95zgpm-control-plane-5cqp6" not found [1mSTEP[0m: Error starting logs stream for pod kube-system/kube-proxy-tzrmc, container kube-proxy: pods "node-drain-95zgpm-control-plane-5cqp6" not found [1mSTEP[0m: Error starting logs stream for pod kube-system/kube-scheduler-node-drain-95zgpm-control-plane-5cqp6, container kube-scheduler: pods "node-drain-95zgpm-control-plane-5cqp6" not found [1mSTEP[0m: Error starting logs stream for pod kube-system/etcd-node-drain-95zgpm-control-plane-5cqp6, container etcd: pods "node-drain-95zgpm-control-plane-5cqp6" not found [1mSTEP[0m: Fetching activity logs took 3.201627276s [1mSTEP[0m: Dumping all the Cluster API resources in the "node-drain-7yhoyy" namespace [1mSTEP[0m: Deleting cluster node-drain-7yhoyy/node-drain-95zgpm [1mSTEP[0m: Deleting cluster node-drain-95zgpm INFO: Waiting for the Cluster node-drain-7yhoyy/node-drain-95zgpm to be deleted [1mSTEP[0m: Waiting for cluster node-drain-95zgpm to be deleted ... skipping 84 lines ... [1mSTEP[0m: Collecting events for Pod kube-system/kube-scheduler-machine-pool-ank0hs-control-plane-l2hks [1mSTEP[0m: Collecting events for Pod kube-system/calico-kube-controllers-85f479877b-bqclt [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-4vdjf, container calico-node [1mSTEP[0m: Collecting events for Pod kube-system/calico-node-wnhqt [1mSTEP[0m: Collecting events for Pod kube-system/coredns-bd6b6df9f-mmrkm [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-vxhp2, container kube-proxy [1mSTEP[0m: failed to find events of Pod "kube-scheduler-machine-pool-ank0hs-control-plane-l2hks" [1mSTEP[0m: Collecting events for Pod kube-system/kube-apiserver-machine-pool-ank0hs-control-plane-l2hks [1mSTEP[0m: Creating log watcher for controller kube-system/coredns-bd6b6df9f-k8xqd, container coredns [1mSTEP[0m: failed to find events of Pod "kube-apiserver-machine-pool-ank0hs-control-plane-l2hks" [1mSTEP[0m: failed to find events of Pod "etcd-machine-pool-ank0hs-control-plane-l2hks" [1mSTEP[0m: Dumping workload cluster machine-pool-tbvo1r/machine-pool-ank0hs Azure activity log [1mSTEP[0m: Creating log watcher for controller kube-system/kube-apiserver-machine-pool-ank0hs-control-plane-l2hks, container kube-apiserver [1mSTEP[0m: Creating log watcher for controller kube-system/etcd-machine-pool-ank0hs-control-plane-l2hks, container etcd [1mSTEP[0m: Creating log watcher for controller kube-system/coredns-bd6b6df9f-mmrkm, container coredns [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-5hrj6, container kube-proxy [1mSTEP[0m: Collecting events for Pod kube-system/kube-controller-manager-machine-pool-ank0hs-control-plane-l2hks [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-windows-79mns, container kube-proxy [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-windows-ttk9p, container calico-node-startup [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-windows-79mns [1mSTEP[0m: Creating log watcher for controller kube-system/kube-scheduler-machine-pool-ank0hs-control-plane-l2hks, container kube-scheduler [1mSTEP[0m: failed to find events of Pod "kube-controller-manager-machine-pool-ank0hs-control-plane-l2hks" [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-vxhp2 [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-windows-ttk9p, container calico-node-felix [1mSTEP[0m: Collecting events for Pod kube-system/calico-node-4vdjf [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-wnhqt, container calico-node [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-5hrj6 [1mSTEP[0m: Error starting logs stream for pod kube-system/kube-proxy-windows-79mns, container kube-proxy: pods "win-p-win000002" not found [1mSTEP[0m: Error starting logs stream for pod kube-system/calico-node-windows-ttk9p, container calico-node-startup: pods "win-p-win000002" not found [1mSTEP[0m: Error starting logs stream for pod kube-system/calico-node-4vdjf, container calico-node: pods "machine-pool-ank0hs-mp-0000002" not found [1mSTEP[0m: Error starting logs stream for pod kube-system/kube-proxy-vxhp2, container kube-proxy: pods "machine-pool-ank0hs-mp-0000002" not found [1mSTEP[0m: Error starting logs stream for pod kube-system/calico-node-windows-ttk9p, container calico-node-felix: pods "win-p-win000002" not found [1mSTEP[0m: Fetching activity logs took 1.87844724s [1mSTEP[0m: Dumping all the Cluster API resources in the "machine-pool-tbvo1r" namespace [1mSTEP[0m: Deleting cluster machine-pool-tbvo1r/machine-pool-ank0hs [1mSTEP[0m: Deleting cluster machine-pool-ank0hs INFO: Waiting for the Cluster machine-pool-tbvo1r/machine-pool-ank0hs to be deleted [1mSTEP[0m: Waiting for cluster machine-pool-ank0hs to be deleted ... skipping 78 lines ... Dec 27 21:22:19.296: INFO: Collecting logs for Windows node md-scale-fmpvs in cluster md-scale-bsb3l6 in namespace md-scale-764q8o Dec 27 21:24:58.503: INFO: Attempting to copy file /c:/crashdumps.tar on node md-scale-fmpvs to /logs/artifacts/clusters/md-scale-bsb3l6/machines/md-scale-bsb3l6-md-win-6c878589b7-9s994/crashdumps.tar Dec 27 21:25:00.371: INFO: Collecting boot logs for AzureMachine md-scale-bsb3l6-md-win-fmpvs Failed to get logs for machine md-scale-bsb3l6-md-win-6c878589b7-9s994, cluster md-scale-764q8o/md-scale-bsb3l6: [running command "Get-Content "C:\\cni.log"": Process exited with status 1, running command "$p = 'c:\localdumps' ; if (Test-Path $p) { tar.exe -cvzf c:\crashdumps.tar $p *>&1 | %{ Write-Output "$_"} } else { Write-Host "No crash dumps found at $p" }": Process exited with status 1] Dec 27 21:25:01.350: INFO: Collecting logs for Windows node md-scale-kzjtw in cluster md-scale-bsb3l6 in namespace md-scale-764q8o Dec 27 21:27:42.147: INFO: Attempting to copy file /c:/crashdumps.tar on node md-scale-kzjtw to /logs/artifacts/clusters/md-scale-bsb3l6/machines/md-scale-bsb3l6-md-win-6c878589b7-v77pr/crashdumps.tar Dec 27 21:27:43.979: INFO: Collecting boot logs for AzureMachine md-scale-bsb3l6-md-win-kzjtw Failed to get logs for machine md-scale-bsb3l6-md-win-6c878589b7-v77pr, cluster md-scale-764q8o/md-scale-bsb3l6: [running command "Get-Content "C:\\cni.log"": Process exited with status 1, running command "$p = 'c:\localdumps' ; if (Test-Path $p) { tar.exe -cvzf c:\crashdumps.tar $p *>&1 | %{ Write-Output "$_"} } else { Write-Host "No crash dumps found at $p" }": Process exited with status 1] [1mSTEP[0m: Dumping workload cluster md-scale-764q8o/md-scale-bsb3l6 kube-system pod logs [1mSTEP[0m: Collecting events for Pod kube-system/containerd-logger-26x9c [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-windows-plxx7, container calico-node-startup [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-windows-plxx7, container calico-node-felix [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-4qfwc, container calico-node [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-ntvpl, container calico-node ... skipping 52 lines ... [90m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/capi_test.go:45[0m Should successfully scale out and scale in a MachineDeployment [90m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/capi_test.go:171[0m Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count [90m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.6/e2e/md_scale.go:71[0m [90m------------------------------[0m {"component":"entrypoint","file":"k8s.io/test-infra/prow/entrypoint/run.go:164","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Process did not finish before 4h0m0s timeout","severity":"error","time":"2022-12-28T01:02:37Z"} ++ early_exit_handler ++ '[' -n 163 ']' ++ kill -TERM 163 ++ cleanup_dind ++ [[ true == \t\r\u\e ]] ++ echo 'Cleaning up after docker' ... skipping 12 lines ... Cleaning up after docker Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? Stopping Docker: dockerProgram process in pidfile '/var/run/docker-ssd.pid', 1 process(es), refused to die. ================================================================================ Done cleaning up after docker in docker. All sensitive variables are redacted {"component":"entrypoint","file":"k8s.io/test-infra/prow/entrypoint/run.go:254","func":"k8s.io/test-infra/prow/entrypoint.gracefullyTerminate","level":"error","msg":"Process did not exit before 15m0s grace period","severity":"error","time":"2022-12-28T01:17:37Z"} {"component":"entrypoint","error":"os: process already finished","file":"k8s.io/test-infra/prow/entrypoint/run.go:256","func":"k8s.io/test-infra/prow/entrypoint.gracefullyTerminate","level":"error","msg":"Could not kill process after grace period","severity":"error","time":"2022-12-28T01:17:37Z"}