This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 7 succeeded
Started2022-09-28 20:37
Elapsed4h15m
Revisionrelease-1.5

No Test Failures!


Show 7 Passed Tests

Show 14 Skipped Tests

Error lines from build-log.txt

... skipping 596 lines ...
STEP: Creating log watcher for controller kube-system/kube-scheduler-kcp-adoption-uvokmr-control-plane-0, container kube-scheduler
STEP: Dumping workload cluster kcp-adoption-zb9in8/kcp-adoption-uvokmr Azure activity log
STEP: Creating log watcher for controller kube-system/calico-node-w7sg5, container calico-node
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-85f479877b-ghjtz, container calico-kube-controllers
STEP: Creating log watcher for controller kube-system/coredns-64897985d-f7v2l, container coredns
STEP: Collecting events for Pod kube-system/kube-apiserver-kcp-adoption-uvokmr-control-plane-0
STEP: failed to find events of Pod "kube-apiserver-kcp-adoption-uvokmr-control-plane-0"
STEP: Creating log watcher for controller kube-system/kube-controller-manager-kcp-adoption-uvokmr-control-plane-0, container kube-controller-manager
STEP: Collecting events for Pod kube-system/kube-controller-manager-kcp-adoption-uvokmr-control-plane-0
STEP: Collecting events for Pod kube-system/coredns-64897985d-wvflt
STEP: Collecting events for Pod kube-system/coredns-64897985d-f7v2l
STEP: Collecting events for Pod kube-system/calico-node-w7sg5
STEP: Creating log watcher for controller kube-system/coredns-64897985d-wvflt, container coredns
... skipping 26 lines ...
  Should pivot the bootstrap cluster to a self-hosted cluster
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_selfhosted.go:107

INFO: "Should pivot the bootstrap cluster to a self-hosted cluster" started at Wed, 28 Sep 2022 20:47:41 UTC on Ginkgo node 4 of 10
STEP: Creating namespace "self-hosted" for hosting the cluster
Sep 28 20:47:41.925: INFO: starting to create namespace for hosting the "self-hosted" test spec
2022/09/28 20:47:41 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"
STEP: Creating a workload cluster
INFO: Creating the workload cluster with name "self-hosted-t3plbg" using the "management" template (Kubernetes v1.23.12, 1 control-plane machines, 1 worker machines)
INFO: Getting the cluster template yaml
INFO: clusterctl config cluster self-hosted-t3plbg --infrastructure (default) --kubernetes-version v1.23.12 --control-plane-machine-count 1 --worker-machine-count 1 --flavor management
... skipping 62 lines ...
STEP: Fetching kube-system pod logs took 373.028162ms
STEP: Collecting events for Pod kube-system/etcd-self-hosted-t3plbg-control-plane-5mr5l
STEP: Creating log watcher for controller kube-system/kube-scheduler-self-hosted-t3plbg-control-plane-5mr5l, container kube-scheduler
STEP: Collecting events for Pod kube-system/coredns-64897985d-gq7j7
STEP: Creating log watcher for controller kube-system/kube-proxy-7chkw, container kube-proxy
STEP: Collecting events for Pod kube-system/coredns-64897985d-hxld6
STEP: failed to find events of Pod "etcd-self-hosted-t3plbg-control-plane-5mr5l"
STEP: Creating log watcher for controller kube-system/calico-node-hsf7z, container calico-node
STEP: Creating log watcher for controller kube-system/etcd-self-hosted-t3plbg-control-plane-5mr5l, container etcd
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-85f479877b-phrfh, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/kube-controller-manager-self-hosted-t3plbg-control-plane-5mr5l
STEP: Creating log watcher for controller kube-system/calico-node-fjf6c, container calico-node
STEP: Collecting events for Pod kube-system/calico-node-fjf6c
STEP: failed to find events of Pod "kube-controller-manager-self-hosted-t3plbg-control-plane-5mr5l"
STEP: Collecting events for Pod kube-system/calico-kube-controllers-85f479877b-phrfh
STEP: Creating log watcher for controller kube-system/coredns-64897985d-hxld6, container coredns
STEP: Collecting events for Pod kube-system/calico-node-hsf7z
STEP: Creating log watcher for controller kube-system/kube-apiserver-self-hosted-t3plbg-control-plane-5mr5l, container kube-apiserver
STEP: Collecting events for Pod kube-system/kube-proxy-7chkw
STEP: Creating log watcher for controller kube-system/kube-proxy-pp8mk, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-apiserver-self-hosted-t3plbg-control-plane-5mr5l
STEP: failed to find events of Pod "kube-apiserver-self-hosted-t3plbg-control-plane-5mr5l"
STEP: Creating log watcher for controller kube-system/kube-controller-manager-self-hosted-t3plbg-control-plane-5mr5l, container kube-controller-manager
STEP: Collecting events for Pod kube-system/kube-proxy-pp8mk
STEP: Collecting events for Pod kube-system/kube-scheduler-self-hosted-t3plbg-control-plane-5mr5l
STEP: failed to find events of Pod "kube-scheduler-self-hosted-t3plbg-control-plane-5mr5l"
STEP: Creating log watcher for controller kube-system/coredns-64897985d-gq7j7, container coredns
STEP: Dumping workload cluster self-hosted/self-hosted-t3plbg Azure activity log
STEP: Fetching activity logs took 1.818706718s
Sep 28 20:57:16.701: INFO: Dumping all the Cluster API resources in the "self-hosted" namespace
Sep 28 20:57:17.050: INFO: Deleting all clusters in the self-hosted namespace
STEP: Deleting cluster self-hosted-t3plbg
INFO: Waiting for the Cluster self-hosted/self-hosted-t3plbg to be deleted
STEP: Waiting for cluster self-hosted-t3plbg to be deleted
INFO: Got error while streaming logs for pod capi-system/capi-controller-manager-7df9bc44b4-dtzxz, container manager: http2: client connection lost
INFO: Got error while streaming logs for pod capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager-6c76c59d6b-tzk4g, 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-74b6b6b77f-pdmzz, container manager: http2: client connection lost
INFO: Got error while streaming logs for pod capz-system/capz-controller-manager-c9ccb6694-lwhnq, container manager: http2: client connection lost
Sep 28 21:01:07.238: INFO: Deleting namespace used for hosting the "self-hosted" test spec
INFO: Deleting namespace self-hosted
Sep 28 21:01:07.258: INFO: Checking if any resources are left over in Azure for spec "self-hosted"
STEP: Redacting sensitive information from logs
Sep 28 21:01:34.274: 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
STEP: Redacting sensitive information from logs
... skipping 67 lines ...
STEP: Dumping workload cluster mhc-remediation-w41g4k/mhc-remediation-aaujxn kube-system pod logs
STEP: Fetching kube-system pod logs took 469.250528ms
STEP: Creating log watcher for controller kube-system/calico-node-kb9hc, container calico-node
STEP: Collecting events for Pod kube-system/etcd-mhc-remediation-aaujxn-control-plane-qrr8s
STEP: Creating log watcher for controller kube-system/kube-proxy-6htnl, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-apiserver-mhc-remediation-aaujxn-control-plane-qrr8s
STEP: failed to find events of Pod "etcd-mhc-remediation-aaujxn-control-plane-qrr8s"
STEP: Creating log watcher for controller kube-system/kube-apiserver-mhc-remediation-aaujxn-control-plane-qrr8s, container kube-apiserver
STEP: Collecting events for Pod kube-system/kube-proxy-z8k9c
STEP: failed to find events of Pod "kube-apiserver-mhc-remediation-aaujxn-control-plane-qrr8s"
STEP: Creating log watcher for controller kube-system/kube-scheduler-mhc-remediation-aaujxn-control-plane-qrr8s, container kube-scheduler
STEP: Collecting events for Pod kube-system/kube-scheduler-mhc-remediation-aaujxn-control-plane-qrr8s
STEP: failed to find events of Pod "kube-scheduler-mhc-remediation-aaujxn-control-plane-qrr8s"
STEP: Creating log watcher for controller kube-system/kube-controller-manager-mhc-remediation-aaujxn-control-plane-qrr8s, container kube-controller-manager
STEP: Dumping workload cluster mhc-remediation-w41g4k/mhc-remediation-aaujxn Azure activity log
STEP: Collecting events for Pod kube-system/kube-controller-manager-mhc-remediation-aaujxn-control-plane-qrr8s
STEP: failed to find events of Pod "kube-controller-manager-mhc-remediation-aaujxn-control-plane-qrr8s"
STEP: Collecting events for Pod kube-system/calico-kube-controllers-85f479877b-bdr4c
STEP: Collecting events for Pod kube-system/calico-node-kb9hc
STEP: Creating log watcher for controller kube-system/calico-node-kxmxx, container calico-node
STEP: Collecting events for Pod kube-system/calico-node-kxmxx
STEP: Creating log watcher for controller kube-system/coredns-64897985d-9w8rc, container coredns
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-85f479877b-bdr4c, container calico-kube-controllers
... skipping 101 lines ...
STEP: Creating log watcher for controller kube-system/coredns-64897985d-gmr48, container coredns
STEP: Creating log watcher for controller kube-system/kube-proxy-pvzbc, container kube-proxy
STEP: Creating log watcher for controller kube-system/etcd-machine-pool-2vip80-control-plane-5mtx7, container etcd
STEP: Collecting events for Pod kube-system/calico-node-windows-mnjnn
STEP: Creating log watcher for controller kube-system/kube-apiserver-machine-pool-2vip80-control-plane-5mtx7, container kube-apiserver
STEP: Collecting events for Pod kube-system/etcd-machine-pool-2vip80-control-plane-5mtx7
STEP: failed to find events of Pod "etcd-machine-pool-2vip80-control-plane-5mtx7"
STEP: Collecting events for Pod kube-system/kube-controller-manager-machine-pool-2vip80-control-plane-5mtx7
STEP: Creating log watcher for controller kube-system/kube-scheduler-machine-pool-2vip80-control-plane-5mtx7, container kube-scheduler
STEP: Collecting events for Pod kube-system/kube-proxy-windows-kzv6n
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-kzv6n, container kube-proxy
STEP: Creating log watcher for controller kube-system/coredns-64897985d-xmbls, container coredns
STEP: Creating log watcher for controller kube-system/kube-controller-manager-machine-pool-2vip80-control-plane-5mtx7, container kube-controller-manager
STEP: Collecting events for Pod kube-system/kube-proxy-pvzbc
STEP: Collecting events for Pod kube-system/kube-apiserver-machine-pool-2vip80-control-plane-5mtx7
STEP: Collecting events for Pod kube-system/kube-proxy-sxv9p
STEP: Creating log watcher for controller kube-system/kube-proxy-sxv9p, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-scheduler-machine-pool-2vip80-control-plane-5mtx7
STEP: failed to find events of Pod "kube-scheduler-machine-pool-2vip80-control-plane-5mtx7"
STEP: failed to find events of Pod "kube-controller-manager-machine-pool-2vip80-control-plane-5mtx7"
STEP: Collecting events for Pod kube-system/coredns-64897985d-gmr48
STEP: Error starting logs stream for pod kube-system/calico-node-82ld8, container calico-node: pods "machine-pool-2vip80-mp-0000002" not found
STEP: Error starting logs stream for pod kube-system/calico-node-windows-mnjnn, container calico-node-startup: pods "win-p-win000002" not found
STEP: Error starting logs stream for pod kube-system/calico-node-windows-mnjnn, container calico-node-felix: pods "win-p-win000002" not found
STEP: Error starting logs stream for pod kube-system/kube-proxy-sxv9p, container kube-proxy: pods "machine-pool-2vip80-mp-0000002" not found
STEP: Error starting logs stream for pod kube-system/kube-proxy-windows-kzv6n, container kube-proxy: pods "win-p-win000002" not found
STEP: Fetching activity logs took 1.4521397s
STEP: Dumping all the Cluster API resources in the "machine-pool-nzrjra" namespace
STEP: Deleting cluster machine-pool-nzrjra/machine-pool-2vip80
STEP: Deleting cluster machine-pool-2vip80
INFO: Waiting for the Cluster machine-pool-nzrjra/machine-pool-2vip80 to be deleted
STEP: Waiting for cluster machine-pool-2vip80 to be deleted
... skipping 72 lines ...

Sep 28 20:56:57.114: INFO: Collecting logs for Windows node quick-sta-c7rqm in cluster quick-start-cnubmc in namespace quick-start-0jr66u

Sep 28 20:59:38.077: INFO: Attempting to copy file /c:/crashdumps.tar on node quick-sta-c7rqm to /logs/artifacts/clusters/quick-start-cnubmc/machines/quick-start-cnubmc-md-win-56f8b57d78-8wnw4/crashdumps.tar
Sep 28 20:59:40.464: INFO: Collecting boot logs for AzureMachine quick-start-cnubmc-md-win-c7rqm

Failed to get logs for machine quick-start-cnubmc-md-win-56f8b57d78-8wnw4, cluster quick-start-0jr66u/quick-start-cnubmc: [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]
Sep 28 20:59:41.268: INFO: Collecting logs for Windows node quick-sta-vgxbp in cluster quick-start-cnubmc in namespace quick-start-0jr66u

Sep 28 21:02:25.966: INFO: Attempting to copy file /c:/crashdumps.tar on node quick-sta-vgxbp to /logs/artifacts/clusters/quick-start-cnubmc/machines/quick-start-cnubmc-md-win-56f8b57d78-jmv9s/crashdumps.tar
Sep 28 21:02:28.377: INFO: Collecting boot logs for AzureMachine quick-start-cnubmc-md-win-vgxbp

Failed to get logs for machine quick-start-cnubmc-md-win-56f8b57d78-jmv9s, cluster quick-start-0jr66u/quick-start-cnubmc: [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]
STEP: Dumping workload cluster quick-start-0jr66u/quick-start-cnubmc kube-system pod logs
STEP: Collecting events for Pod kube-system/calico-node-2vzcd
STEP: Creating log watcher for controller kube-system/calico-node-windows-qqsgn, container calico-node-startup
STEP: Creating log watcher for controller kube-system/csi-proxy-l8ptm, container csi-proxy
STEP: Collecting events for Pod kube-system/calico-kube-controllers-85f479877b-hjhzm
STEP: Creating log watcher for controller kube-system/containerd-logger-cmkxd, container containerd-logger
... skipping 18 lines ...
STEP: Creating log watcher for controller kube-system/kube-scheduler-quick-start-cnubmc-control-plane-cvl8t, container kube-scheduler
STEP: Collecting events for Pod kube-system/coredns-64897985d-f47jv
STEP: Collecting events for Pod kube-system/kube-proxy-windows-6lgp6
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-6lgp6, container kube-proxy
STEP: Creating log watcher for controller kube-system/coredns-64897985d-f47jv, container coredns
STEP: Collecting events for Pod kube-system/kube-scheduler-quick-start-cnubmc-control-plane-cvl8t
STEP: failed to find events of Pod "kube-scheduler-quick-start-cnubmc-control-plane-cvl8t"
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-bks55, container kube-proxy
STEP: Collecting events for Pod kube-system/calico-node-6fdjz
STEP: Creating log watcher for controller kube-system/kube-apiserver-quick-start-cnubmc-control-plane-cvl8t, container kube-apiserver
STEP: Collecting events for Pod kube-system/kube-apiserver-quick-start-cnubmc-control-plane-cvl8t
STEP: failed to find events of Pod "kube-apiserver-quick-start-cnubmc-control-plane-cvl8t"
STEP: Collecting events for Pod kube-system/kube-proxy-windows-bks55
STEP: Collecting events for Pod kube-system/kube-controller-manager-quick-start-cnubmc-control-plane-cvl8t
STEP: Creating log watcher for controller kube-system/kube-controller-manager-quick-start-cnubmc-control-plane-cvl8t, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/kube-proxy-l9wkc, container kube-proxy
STEP: Collecting events for Pod kube-system/coredns-64897985d-c5tjl
STEP: Collecting events for Pod kube-system/csi-proxy-r7tr5
STEP: Collecting events for Pod kube-system/kube-proxy-wqcvv
STEP: failed to find events of Pod "kube-controller-manager-quick-start-cnubmc-control-plane-cvl8t"
STEP: Collecting events for Pod kube-system/etcd-quick-start-cnubmc-control-plane-cvl8t
STEP: failed to find events of Pod "etcd-quick-start-cnubmc-control-plane-cvl8t"
STEP: Creating log watcher for controller kube-system/etcd-quick-start-cnubmc-control-plane-cvl8t, container etcd
STEP: Fetching activity logs took 1.361291491s
STEP: Dumping all the Cluster API resources in the "quick-start-0jr66u" namespace
STEP: Deleting cluster quick-start-0jr66u/quick-start-cnubmc
STEP: Deleting cluster quick-start-cnubmc
INFO: Waiting for the Cluster quick-start-0jr66u/quick-start-cnubmc to be deleted
... skipping 215 lines ...

Sep 28 20:59:10.302: INFO: Collecting logs for Windows node md-scale-v5vpt in cluster md-scale-lx8mjg in namespace md-scale-hoj903

Sep 28 21:01:56.019: INFO: Attempting to copy file /c:/crashdumps.tar on node md-scale-v5vpt to /logs/artifacts/clusters/md-scale-lx8mjg/machines/md-scale-lx8mjg-md-win-5d75d9b68d-dr9s4/crashdumps.tar
Sep 28 21:01:58.478: INFO: Collecting boot logs for AzureMachine md-scale-lx8mjg-md-win-v5vpt

Failed to get logs for machine md-scale-lx8mjg-md-win-5d75d9b68d-dr9s4, cluster md-scale-hoj903/md-scale-lx8mjg: [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]
Sep 28 21:01:59.439: INFO: Collecting logs for Windows node md-scale-l8dfk in cluster md-scale-lx8mjg in namespace md-scale-hoj903

Sep 28 21:04:43.326: INFO: Attempting to copy file /c:/crashdumps.tar on node md-scale-l8dfk to /logs/artifacts/clusters/md-scale-lx8mjg/machines/md-scale-lx8mjg-md-win-5d75d9b68d-rr2s4/crashdumps.tar
Sep 28 21:04:45.818: INFO: Collecting boot logs for AzureMachine md-scale-lx8mjg-md-win-l8dfk

Failed to get logs for machine md-scale-lx8mjg-md-win-5d75d9b68d-rr2s4, cluster md-scale-hoj903/md-scale-lx8mjg: [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]
STEP: Dumping workload cluster md-scale-hoj903/md-scale-lx8mjg kube-system pod logs
STEP: Fetching kube-system pod logs took 662.416929ms
STEP: Collecting events for Pod kube-system/calico-node-windows-mhmbv
STEP: Creating log watcher for controller kube-system/csi-proxy-j9qn2, container csi-proxy
STEP: Creating log watcher for controller kube-system/calico-node-296xv, container calico-node
STEP: Collecting events for Pod kube-system/calico-node-pzlp7
... skipping 10 lines ...
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-85f479877b-vbklc, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/etcd-md-scale-lx8mjg-control-plane-2ddmp
STEP: Collecting events for Pod kube-system/csi-proxy-j9qn2
STEP: Creating log watcher for controller kube-system/kube-proxy-d9dlz, container kube-proxy
STEP: Creating log watcher for controller kube-system/csi-proxy-m6mnf, container csi-proxy
STEP: Collecting events for Pod kube-system/kube-apiserver-md-scale-lx8mjg-control-plane-2ddmp
STEP: failed to find events of Pod "etcd-md-scale-lx8mjg-control-plane-2ddmp"
STEP: Collecting events for Pod kube-system/csi-proxy-m6mnf
STEP: Collecting events for Pod kube-system/kube-proxy-l279k
STEP: Collecting events for Pod kube-system/kube-proxy-windows-njwsx
STEP: failed to find events of Pod "kube-apiserver-md-scale-lx8mjg-control-plane-2ddmp"
STEP: Creating log watcher for controller kube-system/calico-node-windows-mhmbv, container calico-node-felix
STEP: Creating log watcher for controller kube-system/etcd-md-scale-lx8mjg-control-plane-2ddmp, container etcd
STEP: Creating log watcher for controller kube-system/kube-scheduler-md-scale-lx8mjg-control-plane-2ddmp, container kube-scheduler
STEP: Collecting events for Pod kube-system/kube-scheduler-md-scale-lx8mjg-control-plane-2ddmp
STEP: Collecting events for Pod kube-system/kube-proxy-windows-zhpx2
STEP: Collecting events for Pod kube-system/kube-controller-manager-md-scale-lx8mjg-control-plane-2ddmp
STEP: Collecting events for Pod kube-system/calico-kube-controllers-85f479877b-vbklc
STEP: Collecting events for Pod kube-system/containerd-logger-6f6kl
STEP: Collecting events for Pod kube-system/coredns-64897985d-6x896
STEP: Creating log watcher for controller kube-system/coredns-64897985d-gx4t2, container coredns
STEP: failed to find events of Pod "kube-controller-manager-md-scale-lx8mjg-control-plane-2ddmp"
STEP: Collecting events for Pod kube-system/calico-node-windows-hf29w
STEP: Collecting events for Pod kube-system/coredns-64897985d-gx4t2
STEP: Creating log watcher for controller kube-system/kube-apiserver-md-scale-lx8mjg-control-plane-2ddmp, container kube-apiserver
STEP: Creating log watcher for controller kube-system/kube-controller-manager-md-scale-lx8mjg-control-plane-2ddmp, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-zhpx2, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-njwsx, container kube-proxy
... skipping 75 lines ...
STEP: Dumping logs from the "node-drain-mwy6hx" workload cluster
STEP: Dumping workload cluster node-drain-ztfzfo/node-drain-mwy6hx logs
Sep 28 21:06:42.887: INFO: Collecting logs for Linux node node-drain-mwy6hx-control-plane-82ftt in cluster node-drain-mwy6hx in namespace node-drain-ztfzfo

Sep 28 21:13:18.366: INFO: Collecting boot logs for AzureMachine node-drain-mwy6hx-control-plane-82ftt

Failed to get logs for machine node-drain-mwy6hx-control-plane-pqpvr, cluster node-drain-ztfzfo/node-drain-mwy6hx: dialing public load balancer at node-drain-mwy6hx-1402ad2f.westus2.cloudapp.azure.com: dial tcp 20.112.63.161:22: connect: connection timed out
STEP: Dumping workload cluster node-drain-ztfzfo/node-drain-mwy6hx kube-system pod logs
STEP: Fetching kube-system pod logs took 626.359711ms
STEP: Dumping workload cluster node-drain-ztfzfo/node-drain-mwy6hx Azure activity log
STEP: Creating log watcher for controller kube-system/etcd-node-drain-mwy6hx-control-plane-82ftt, container etcd
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-85f479877b-ws5hv, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/etcd-node-drain-mwy6hx-control-plane-82ftt
... skipping 30 lines ...
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/capi_test.go:45
  Should successfully set and use node drain timeout
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/capi_test.go:195
    A node should be forcefully removed if it cannot be drained in time
    /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.2.1/e2e/node_drain_timeout.go:83
------------------------------
{"component":"entrypoint","file":"k8s.io/test-infra/prow/entrypoint/run.go:165","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Process did not finish before 4h0m0s timeout","severity":"error","time":"2022-09-29T00:37:31Z"}
++ early_exit_handler
++ '[' -n 161 ']'
++ kill -TERM 161
++ 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:255","func":"k8s.io/test-infra/prow/entrypoint.gracefullyTerminate","level":"error","msg":"Process did not exit before 15m0s grace period","severity":"error","time":"2022-09-29T00:52:31Z"}
{"component":"entrypoint","error":"os: process already finished","file":"k8s.io/test-infra/prow/entrypoint/run.go:257","func":"k8s.io/test-infra/prow/entrypoint.gracefullyTerminate","level":"error","msg":"Could not kill process after grace period","severity":"error","time":"2022-09-29T00:52:31Z"}