periodic-cluster-api-provider-azure-capi-e2e-v1beta1 #1610018756304572416
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
capz-e2e Workload cluster creation Creating a GPU-enabled cluster [OPTIONAL] with a single control plane node and 1 node
capz-e2e Workload cluster creation Creating a VMSS cluster [REQUIRED] with a single control plane node and an AzureMachinePool with 2 Linux and 2 Windows worker nodes
capz-e2e Workload cluster creation Creating a cluster that uses the external cloud provider and external azurediskcsi driver [OPTIONAL] with a 1 control plane nodes and 2 worker nodes
capz-e2e Workload cluster creation Creating a dual-stack cluster [OPTIONAL] With dual-stack worker node
capz-e2e Workload cluster creation Creating a highly available cluster [REQUIRED] With 3 control-plane nodes and 2 Linux and 2 Windows worker nodes
capz-e2e Workload cluster creation Creating a ipv6 control-plane cluster [REQUIRED] With ipv6 worker node
capz-e2e Workload cluster creation Creating a private cluster [OPTIONAL] Creates a public management cluster in a custom vnet
capz-e2e Workload cluster creation Creating an AKS cluster [EXPERIMENTAL][Managed Kubernetes] with a single control plane node and 1 node
capz-e2e Workload cluster creation Creating clusters using clusterclass [OPTIONAL] with a single control plane node, one linux worker node, and one windows worker node
capz-e2e [K8s-Upgrade] Running the workload cluster upgrade tests [CSI Migration] Running CSI migration test CSI=external CCM=external AzureDiskCSIMigration=true: upgrade to v1.23 should create volumes dynamically with intree cloud provider
capz-e2e [K8s-Upgrade] Running the workload cluster upgrade tests [CSI Migration] Running CSI migration test CSI=external CCM=internal AzureDiskCSIMigration=true: upgrade to v1.23 should create volumes dynamically with intree cloud provider
capz-e2e [K8s-Upgrade] Running the workload cluster upgrade tests [CSI Migration] Running CSI migration test CSI=internal CCM=internal AzureDiskCSIMigration=false: upgrade to v1.23 should create volumes dynamically with intree cloud provider
... skipping 589 lines ... [1mSTEP[0m: Dumping workload cluster mhc-remediation-itat7j/mhc-remediation-g2rckk kube-system pod logs [1mSTEP[0m: Fetching kube-system pod logs took 234.812039ms [1mSTEP[0m: Dumping workload cluster mhc-remediation-itat7j/mhc-remediation-g2rckk Azure activity log [1mSTEP[0m: Collecting events for Pod kube-system/etcd-mhc-remediation-g2rckk-control-plane-8b9qs [1mSTEP[0m: Creating log watcher for controller kube-system/kube-controller-manager-mhc-remediation-g2rckk-control-plane-8b9qs, container kube-controller-manager [1mSTEP[0m: failed to find events of Pod "etcd-mhc-remediation-g2rckk-control-plane-8b9qs" [1mSTEP[0m: Creating log watcher for controller kube-system/kube-apiserver-mhc-remediation-g2rckk-control-plane-8b9qs, container kube-apiserver [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-7dxn4, container kube-proxy [1mSTEP[0m: Collecting events for Pod kube-system/kube-controller-manager-mhc-remediation-g2rckk-control-plane-8b9qs [1mSTEP[0m: failed to find events of Pod "kube-controller-manager-mhc-remediation-g2rckk-control-plane-8b9qs" [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-29vf2, container kube-proxy [1mSTEP[0m: Creating log watcher for controller kube-system/calico-kube-controllers-85f479877b-n2s96, container calico-kube-controllers [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-7dxn4 [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-mr668, container calico-node [1mSTEP[0m: Collecting events for Pod kube-system/calico-node-mr668 [1mSTEP[0m: Creating log watcher for controller kube-system/kube-scheduler-mhc-remediation-g2rckk-control-plane-8b9qs, container kube-scheduler ... skipping 4 lines ... [1mSTEP[0m: Collecting events for Pod kube-system/calico-node-8ltbv [1mSTEP[0m: Creating log watcher for controller kube-system/etcd-mhc-remediation-g2rckk-control-plane-8b9qs, container etcd [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-29vf2 [1mSTEP[0m: Collecting events for Pod kube-system/kube-apiserver-mhc-remediation-g2rckk-control-plane-8b9qs [1mSTEP[0m: Collecting events for Pod kube-system/kube-scheduler-mhc-remediation-g2rckk-control-plane-8b9qs [1mSTEP[0m: Creating log watcher for controller kube-system/coredns-bd6b6df9f-5vhx2, container coredns [1mSTEP[0m: failed to find events of Pod "kube-scheduler-mhc-remediation-g2rckk-control-plane-8b9qs" [1mSTEP[0m: Collecting events for Pod kube-system/calico-kube-controllers-85f479877b-n2s96 [1mSTEP[0m: failed to find events of Pod "kube-apiserver-mhc-remediation-g2rckk-control-plane-8b9qs" [1mSTEP[0m: Fetching activity logs took 1.375789577s [1mSTEP[0m: Dumping all the Cluster API resources in the "mhc-remediation-itat7j" namespace [1mSTEP[0m: Deleting cluster mhc-remediation-itat7j/mhc-remediation-g2rckk [1mSTEP[0m: Deleting cluster mhc-remediation-g2rckk INFO: Waiting for the Cluster mhc-remediation-itat7j/mhc-remediation-g2rckk to be deleted [1mSTEP[0m: Waiting for cluster mhc-remediation-g2rckk to be deleted ... skipping 16 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 Mon, 02 Jan 2023 21:11:49 UTC on Ginkgo node 6 of 10 [1mSTEP[0m: Creating namespace "self-hosted" for hosting the cluster Jan 2 21:11:49.364: INFO: starting to create namespace for hosting the "self-hosted" test spec 2023/01/02 21:11:49 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-pa9vi3" 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-pa9vi3 --infrastructure (default) --kubernetes-version v1.23.15 --control-plane-machine-count 1 --worker-machine-count 1 --flavor management ... skipping 73 lines ... [1mSTEP[0m: Collecting events for Pod kube-system/etcd-self-hosted-pa9vi3-control-plane-5ztgz [1mSTEP[0m: Creating log watcher for controller kube-system/kube-apiserver-self-hosted-pa9vi3-control-plane-5ztgz, container kube-apiserver [1mSTEP[0m: Collecting events for Pod kube-system/coredns-bd6b6df9f-mlt6m [1mSTEP[0m: Collecting events for Pod kube-system/kube-apiserver-self-hosted-pa9vi3-control-plane-5ztgz [1mSTEP[0m: Creating log watcher for controller kube-system/kube-controller-manager-self-hosted-pa9vi3-control-plane-5ztgz, container kube-controller-manager [1mSTEP[0m: Collecting events for Pod kube-system/kube-controller-manager-self-hosted-pa9vi3-control-plane-5ztgz [1mSTEP[0m: failed to find events of Pod "etcd-self-hosted-pa9vi3-control-plane-5ztgz" [1mSTEP[0m: failed to find events of Pod "kube-controller-manager-self-hosted-pa9vi3-control-plane-5ztgz" [1mSTEP[0m: Collecting events for Pod kube-system/kube-scheduler-self-hosted-pa9vi3-control-plane-5ztgz [1mSTEP[0m: failed to find events of Pod "kube-scheduler-self-hosted-pa9vi3-control-plane-5ztgz" [1mSTEP[0m: Creating log watcher for controller kube-system/kube-scheduler-self-hosted-pa9vi3-control-plane-5ztgz, container kube-scheduler [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-f4w7h [1mSTEP[0m: Creating log watcher for controller kube-system/etcd-self-hosted-pa9vi3-control-plane-5ztgz, container etcd [1mSTEP[0m: Collecting events for Pod kube-system/coredns-bd6b6df9f-nf5lw [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-slkb9, container kube-proxy [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-slkb9 [1mSTEP[0m: Fetching activity logs took 1.484499674s Jan 2 21:21:42.088: INFO: Dumping all the Cluster API resources in the "self-hosted" namespace Jan 2 21:21:42.425: INFO: Deleting all clusters in the self-hosted namespace [1mSTEP[0m: Deleting cluster self-hosted-pa9vi3 INFO: Waiting for the Cluster self-hosted/self-hosted-pa9vi3 to be deleted [1mSTEP[0m: Waiting for cluster self-hosted-pa9vi3 to be deleted INFO: Got error while streaming logs for pod capz-system/capz-controller-manager-5487cf5b49-gmgbj, 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-xjw6n, container manager: http2: client connection lost INFO: Got error while streaming logs for pod capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager-8f6f78b8b-t79h4, container manager: http2: client connection lost INFO: Got error while streaming logs for pod capi-system/capi-controller-manager-5b6d47468d-wjr2r, container manager: http2: client connection lost Jan 2 21:26:22.609: INFO: Deleting namespace used for hosting the "self-hosted" test spec INFO: Deleting namespace self-hosted Jan 2 21:26:22.627: INFO: Checking if any resources are left over in Azure for spec "self-hosted" [1mSTEP[0m: Redacting sensitive information from logs Jan 2 21:26:51.681: 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 210 lines ... [1mSTEP[0m: Fetching kube-system pod logs took 442.749933ms [1mSTEP[0m: Collecting events for Pod kube-system/calico-node-windows-lgmw7 [1mSTEP[0m: Collecting events for Pod kube-system/etcd-machine-pool-aaiwbm-control-plane-bd7ds [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-windows-4nvfr, container kube-proxy [1mSTEP[0m: Collecting events for Pod kube-system/coredns-bd6b6df9f-8k4t4 [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-windows-lgmw7, container calico-node-startup [1mSTEP[0m: failed to find events of Pod "etcd-machine-pool-aaiwbm-control-plane-bd7ds" [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-zhb29 [1mSTEP[0m: Creating log watcher for controller kube-system/coredns-bd6b6df9f-8k4t4, container coredns [1mSTEP[0m: Creating log watcher for controller kube-system/coredns-bd6b6df9f-wjskj, container coredns [1mSTEP[0m: Collecting events for Pod kube-system/calico-kube-controllers-85f479877b-lv42c [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-cd4cv, container calico-node [1mSTEP[0m: Creating log watcher for controller kube-system/kube-controller-manager-machine-pool-aaiwbm-control-plane-bd7ds, container kube-controller-manager [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-zhb29, container kube-proxy [1mSTEP[0m: Collecting events for Pod kube-system/kube-controller-manager-machine-pool-aaiwbm-control-plane-bd7ds [1mSTEP[0m: failed to find events of Pod "kube-controller-manager-machine-pool-aaiwbm-control-plane-bd7ds" [1mSTEP[0m: Creating log watcher for controller kube-system/kube-scheduler-machine-pool-aaiwbm-control-plane-bd7ds, container kube-scheduler [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-jxptg, container calico-node [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-windows-4nvfr [1mSTEP[0m: Collecting events for Pod kube-system/calico-node-jxptg [1mSTEP[0m: Creating log watcher for controller kube-system/kube-apiserver-machine-pool-aaiwbm-control-plane-bd7ds, container kube-apiserver [1mSTEP[0m: Collecting events for Pod kube-system/calico-node-cd4cv [1mSTEP[0m: Collecting events for Pod kube-system/kube-apiserver-machine-pool-aaiwbm-control-plane-bd7ds [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-sw8v8, container kube-proxy [1mSTEP[0m: Collecting events for Pod kube-system/kube-scheduler-machine-pool-aaiwbm-control-plane-bd7ds [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-sw8v8 [1mSTEP[0m: failed to find events of Pod "kube-scheduler-machine-pool-aaiwbm-control-plane-bd7ds" [1mSTEP[0m: Dumping workload cluster machine-pool-sdjm1b/machine-pool-aaiwbm Azure activity log [1mSTEP[0m: Creating log watcher for controller kube-system/calico-kube-controllers-85f479877b-lv42c, container calico-kube-controllers [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-windows-lgmw7, container calico-node-felix [1mSTEP[0m: Collecting events for Pod kube-system/coredns-bd6b6df9f-wjskj [1mSTEP[0m: Creating log watcher for controller kube-system/etcd-machine-pool-aaiwbm-control-plane-bd7ds, container etcd [1mSTEP[0m: Error starting logs stream for pod kube-system/calico-node-windows-lgmw7, container calico-node-startup: pods "win-p-win000002" not found [1mSTEP[0m: Error starting logs stream for pod kube-system/kube-proxy-windows-4nvfr, container kube-proxy: pods "win-p-win000002" not found [1mSTEP[0m: Error starting logs stream for pod kube-system/calico-node-jxptg, container calico-node: pods "machine-pool-aaiwbm-mp-0000002" not found [1mSTEP[0m: Error starting logs stream for pod kube-system/kube-proxy-sw8v8, container kube-proxy: pods "machine-pool-aaiwbm-mp-0000002" not found [1mSTEP[0m: Error starting logs stream for pod kube-system/calico-node-windows-lgmw7, container calico-node-felix: pods "win-p-win000002" not found [1mSTEP[0m: Fetching activity logs took 2.059525275s [1mSTEP[0m: Dumping all the Cluster API resources in the "machine-pool-sdjm1b" namespace [1mSTEP[0m: Deleting cluster machine-pool-sdjm1b/machine-pool-aaiwbm [1mSTEP[0m: Deleting cluster machine-pool-aaiwbm INFO: Waiting for the Cluster machine-pool-sdjm1b/machine-pool-aaiwbm to be deleted [1mSTEP[0m: Waiting for cluster machine-pool-aaiwbm to be deleted ... skipping 72 lines ... Jan 2 21:21:19.762: INFO: Collecting logs for Windows node quick-sta-njjtf in cluster quick-start-owikys in namespace quick-start-hs0g6c Jan 2 21:23:49.176: INFO: Attempting to copy file /c:/crashdumps.tar on node quick-sta-njjtf to /logs/artifacts/clusters/quick-start-owikys/machines/quick-start-owikys-md-win-54f86569cf-rbqs4/crashdumps.tar Jan 2 21:23:50.850: INFO: Collecting boot logs for AzureMachine quick-start-owikys-md-win-njjtf Failed to get logs for machine quick-start-owikys-md-win-54f86569cf-rbqs4, cluster quick-start-hs0g6c/quick-start-owikys: [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] Jan 2 21:23:51.827: INFO: Collecting logs for Windows node quick-sta-stlkm in cluster quick-start-owikys in namespace quick-start-hs0g6c Jan 2 21:26:25.701: INFO: Attempting to copy file /c:/crashdumps.tar on node quick-sta-stlkm to /logs/artifacts/clusters/quick-start-owikys/machines/quick-start-owikys-md-win-54f86569cf-t9x25/crashdumps.tar Jan 2 21:26:27.448: INFO: Collecting boot logs for AzureMachine quick-start-owikys-md-win-stlkm Failed to get logs for machine quick-start-owikys-md-win-54f86569cf-t9x25, cluster quick-start-hs0g6c/quick-start-owikys: [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-hs0g6c/quick-start-owikys kube-system pod logs [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-windows-kb8z7, container calico-node-felix [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-windows-n8nvx, container calico-node-startup [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-87xlw, container calico-node [1mSTEP[0m: Collecting events for Pod kube-system/calico-node-87xlw [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-windows-kb8z7, container calico-node-startup ... skipping 4 lines ... [1mSTEP[0m: Collecting events for Pod kube-system/csi-proxy-r2hkm [1mSTEP[0m: Collecting events for Pod kube-system/calico-node-windows-n8nvx [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-xqd76, container calico-node [1mSTEP[0m: Creating log watcher for controller kube-system/etcd-quick-start-owikys-control-plane-t5lcf, container etcd [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-jrrw6 [1mSTEP[0m: Collecting events for Pod kube-system/etcd-quick-start-owikys-control-plane-t5lcf [1mSTEP[0m: failed to find events of Pod "etcd-quick-start-owikys-control-plane-t5lcf" [1mSTEP[0m: Creating log watcher for controller kube-system/kube-apiserver-quick-start-owikys-control-plane-t5lcf, container kube-apiserver [1mSTEP[0m: Collecting events for Pod kube-system/kube-scheduler-quick-start-owikys-control-plane-t5lcf [1mSTEP[0m: Collecting events for Pod kube-system/calico-kube-controllers-85f479877b-7rbwn [1mSTEP[0m: failed to find events of Pod "kube-scheduler-quick-start-owikys-control-plane-t5lcf" [1mSTEP[0m: Collecting events for Pod kube-system/calico-node-windows-kb8z7 [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-windows-wvw4m [1mSTEP[0m: Creating log watcher for controller kube-system/coredns-bd6b6df9f-4nxzx, container coredns [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-windows-rfmc9, container kube-proxy [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-x2cm2, container kube-proxy [1mSTEP[0m: Collecting events for Pod kube-system/kube-apiserver-quick-start-owikys-control-plane-t5lcf [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-windows-rfmc9 [1mSTEP[0m: failed to find events of Pod "kube-apiserver-quick-start-owikys-control-plane-t5lcf" [1mSTEP[0m: Creating log watcher for controller kube-system/kube-controller-manager-quick-start-owikys-control-plane-t5lcf, container kube-controller-manager [1mSTEP[0m: Collecting events for Pod kube-system/containerd-logger-bj7ln [1mSTEP[0m: Collecting events for Pod kube-system/coredns-bd6b6df9f-4nxzx [1mSTEP[0m: Creating log watcher for controller kube-system/containerd-logger-gbg7g, container containerd-logger [1mSTEP[0m: Creating log watcher for controller kube-system/coredns-bd6b6df9f-88wch, container coredns [1mSTEP[0m: Creating log watcher for controller kube-system/kube-scheduler-quick-start-owikys-control-plane-t5lcf, container kube-scheduler [1mSTEP[0m: Collecting events for Pod kube-system/calico-node-xqd76 [1mSTEP[0m: Creating log watcher for controller kube-system/containerd-logger-bj7ln, container containerd-logger [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-windows-wvw4m, container kube-proxy [1mSTEP[0m: Collecting events for Pod kube-system/kube-controller-manager-quick-start-owikys-control-plane-t5lcf [1mSTEP[0m: failed to find events of Pod "kube-controller-manager-quick-start-owikys-control-plane-t5lcf" [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-jrrw6, container kube-proxy [1mSTEP[0m: Collecting events for Pod kube-system/coredns-bd6b6df9f-88wch [1mSTEP[0m: Collecting events for Pod kube-system/csi-proxy-mbnh4 [1mSTEP[0m: Collecting events for Pod kube-system/containerd-logger-gbg7g [1mSTEP[0m: Creating log watcher for controller kube-system/csi-proxy-r2hkm, container csi-proxy [1mSTEP[0m: Creating log watcher for controller kube-system/csi-proxy-mbnh4, container csi-proxy ... skipping 107 lines ... [1mSTEP[0m: Creating log watcher for controller kube-system/kube-proxy-jnbsp, container kube-proxy [1mSTEP[0m: Collecting events for Pod kube-system/kube-controller-manager-node-drain-kt6jjg-control-plane-ccpks [1mSTEP[0m: Creating log watcher for controller kube-system/kube-scheduler-node-drain-kt6jjg-control-plane-ccpks, container kube-scheduler [1mSTEP[0m: Collecting events for Pod kube-system/kube-proxy-jnbsp [1mSTEP[0m: Collecting events for Pod kube-system/coredns-bd6b6df9f-9t4qv [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-22dj2, container calico-node [1mSTEP[0m: Error starting logs stream for pod kube-system/etcd-node-drain-kt6jjg-control-plane-c89nw, container etcd: pods "node-drain-kt6jjg-control-plane-c89nw" not found [1mSTEP[0m: Error starting logs stream for pod kube-system/kube-apiserver-node-drain-kt6jjg-control-plane-c89nw, container kube-apiserver: pods "node-drain-kt6jjg-control-plane-c89nw" not found [1mSTEP[0m: Error starting logs stream for pod kube-system/kube-controller-manager-node-drain-kt6jjg-control-plane-c89nw, container kube-controller-manager: pods "node-drain-kt6jjg-control-plane-c89nw" not found [1mSTEP[0m: Error starting logs stream for pod kube-system/kube-proxy-jnbsp, container kube-proxy: pods "node-drain-kt6jjg-control-plane-c89nw" not found [1mSTEP[0m: Error starting logs stream for pod kube-system/calico-node-8gs5d, container calico-node: pods "node-drain-kt6jjg-control-plane-c89nw" not found [1mSTEP[0m: Error starting logs stream for pod kube-system/kube-scheduler-node-drain-kt6jjg-control-plane-c89nw, container kube-scheduler: pods "node-drain-kt6jjg-control-plane-c89nw" not found [1mSTEP[0m: Fetching activity logs took 4.5417217s [1mSTEP[0m: Dumping all the Cluster API resources in the "node-drain-kqtn5m" namespace [1mSTEP[0m: Deleting cluster node-drain-kqtn5m/node-drain-kt6jjg [1mSTEP[0m: Deleting cluster node-drain-kt6jjg INFO: Waiting for the Cluster node-drain-kqtn5m/node-drain-kt6jjg to be deleted [1mSTEP[0m: Waiting for cluster node-drain-kt6jjg to be deleted ... skipping 78 lines ... Jan 2 21:23:53.703: INFO: Collecting logs for Windows node md-scale-4bklb in cluster md-scale-vcl8vw in namespace md-scale-f087c1 Jan 2 21:26:26.630: INFO: Attempting to copy file /c:/crashdumps.tar on node md-scale-4bklb to /logs/artifacts/clusters/md-scale-vcl8vw/machines/md-scale-vcl8vw-md-win-5d666cb4f-tlszq/crashdumps.tar Jan 2 21:26:28.168: INFO: Collecting boot logs for AzureMachine md-scale-vcl8vw-md-win-4bklb Failed to get logs for machine md-scale-vcl8vw-md-win-5d666cb4f-tlszq, cluster md-scale-f087c1/md-scale-vcl8vw: [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] Jan 2 21:26:29.057: INFO: Collecting logs for Windows node md-scale-lrp5z in cluster md-scale-vcl8vw in namespace md-scale-f087c1 Jan 2 21:29:01.566: INFO: Attempting to copy file /c:/crashdumps.tar on node md-scale-lrp5z to /logs/artifacts/clusters/md-scale-vcl8vw/machines/md-scale-vcl8vw-md-win-5d666cb4f-wwd7q/crashdumps.tar Jan 2 21:29:03.147: INFO: Collecting boot logs for AzureMachine md-scale-vcl8vw-md-win-lrp5z Failed to get logs for machine md-scale-vcl8vw-md-win-5d666cb4f-wwd7q, cluster md-scale-f087c1/md-scale-vcl8vw: [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-f087c1/md-scale-vcl8vw kube-system pod logs [1mSTEP[0m: Collecting events for Pod kube-system/calico-node-windows-fw422 [1mSTEP[0m: Creating log watcher for controller kube-system/containerd-logger-l2lnm, container containerd-logger [1mSTEP[0m: Collecting events for Pod kube-system/calico-node-dn8wh [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-windows-fph7m, container calico-node-startup [1mSTEP[0m: Creating log watcher for controller kube-system/calico-node-windows-fw422, container calico-node-startup ... 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":"2023-01-03T01:02:52Z"} ++ early_exit_handler ++ '[' -n 164 ']' ++ kill -TERM 164 ++ 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":"2023-01-03T01:17:52Z"} {"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":"2023-01-03T01:17:52Z"}