This job view page is being replaced by Spyglass soon. Check out the new job view.
PRCecileRobertMichon: Re-add defaulting for AzureMachineTemplate ssh key
ResultABORTED
Tests 0 failed / 0 succeeded
Started2021-11-01 15:30
Elapsed1h36m
Revision7ca2e2436fa697c568f5996e74f4e34473875378
Refs 1811

No Test Failures!


Error lines from build-log.txt

... skipping 476 lines ...
Nov  1 15:45:35.974: INFO: INFO: Collecting boot logs for AzureMachine quick-start-uedi6t-md-0-jclzn

Nov  1 15:45:36.543: INFO: INFO: Collecting logs for node 10.1.0.6 in cluster quick-start-uedi6t in namespace quick-start-jcbhmy

Nov  1 15:45:57.930: INFO: INFO: Collecting boot logs for AzureMachine quick-start-uedi6t-md-win-n7wsb

Failed to get logs for machine quick-start-uedi6t-md-win-567f8dc97b-4n289, cluster quick-start-jcbhmy/quick-start-uedi6t: [running command "get-eventlog -LogName Application -Source Docker | Select-Object Index, TimeGenerated, EntryType, Message | Sort-Object Index | Format-Table -Wrap -Autosize": Process exited with status 1, running command "docker ps -a": Process exited with status 1]
Nov  1 15:45:58.239: INFO: INFO: Unable to collect logs as node doesn't have addresses
Nov  1 15:45:58.239: INFO: INFO: Collecting logs for node quick-start-uedi6t-md-win-726c5 in cluster quick-start-uedi6t in namespace quick-start-jcbhmy

Nov  1 15:46:02.754: INFO: INFO: Collecting boot logs for AzureMachine quick-start-uedi6t-md-win-726c5

Failed to get logs for machine quick-start-uedi6t-md-win-567f8dc97b-srspg, cluster quick-start-jcbhmy/quick-start-uedi6t: dialing from control plane to target node at quick-start-uedi6t-md-win-726c5: ssh: rejected: connect failed (Temporary failure in name resolution)
STEP: Dumping workload cluster quick-start-jcbhmy/quick-start-uedi6t kube-system pod logs
STEP: Fetching kube-system pod logs took 306.950876ms
STEP: Dumping workload cluster quick-start-jcbhmy/quick-start-uedi6t Azure activity log
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-2kcgl, container coredns
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-fsmb8, container coredns
STEP: Creating log watcher for controller kube-system/calico-node-windows-4t6r7, container calico-node-startup
... skipping 14 lines ...
STEP: Fetching activity logs took 814.449612ms
STEP: Dumping all the Cluster API resources in the "quick-start-jcbhmy" namespace
STEP: Deleting cluster quick-start-jcbhmy/quick-start-uedi6t
STEP: Deleting cluster quick-start-uedi6t
INFO: Waiting for the Cluster quick-start-jcbhmy/quick-start-uedi6t to be deleted
STEP: Waiting for cluster quick-start-uedi6t to be deleted
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-fsmb8, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-quick-start-uedi6t-control-plane-sk5pq, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-quick-start-uedi6t-control-plane-sk5pq, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-846b5f484d-s8w4l, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-4t6r7, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-89s7x, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-quick-start-uedi6t-control-plane-sk5pq, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-726vg, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-6z276, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-zqb2f, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-726vg, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-5xn8t, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-2kcgl, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-4t6r7, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-quick-start-uedi6t-control-plane-sk5pq, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-q5kd7, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-knxhl, container calico-node: http2: client connection lost
STEP: Deleting namespace used for hosting the "quick-start" test spec
INFO: Deleting namespace quick-start-jcbhmy
STEP: Redacting sensitive information from logs


• [SLOW TEST:962.602 seconds]
... skipping 74 lines ...
Nov  1 16:05:48.956: INFO: INFO: Collecting boot logs for AzureMachine kcp-upgrade-xcxahy-md-0-zd69x

Nov  1 16:05:49.293: INFO: INFO: Collecting logs for node 10.1.0.6 in cluster kcp-upgrade-xcxahy in namespace kcp-upgrade-61o13v

Nov  1 16:06:22.424: INFO: INFO: Collecting boot logs for AzureMachine kcp-upgrade-xcxahy-md-win-7dw6n

Failed to get logs for machine kcp-upgrade-xcxahy-md-win-b6bdcc569-cmr7d, cluster kcp-upgrade-61o13v/kcp-upgrade-xcxahy: [running command "get-eventlog -LogName Application -Source Docker | Select-Object Index, TimeGenerated, EntryType, Message | Sort-Object Index | Format-Table -Wrap -Autosize": Process exited with status 1, running command "docker ps -a": Process exited with status 1]
Nov  1 16:06:22.885: INFO: INFO: Collecting logs for node 10.1.0.5 in cluster kcp-upgrade-xcxahy in namespace kcp-upgrade-61o13v

Nov  1 16:06:50.071: INFO: INFO: Collecting boot logs for AzureMachine kcp-upgrade-xcxahy-md-win-cbnth

Failed to get logs for machine kcp-upgrade-xcxahy-md-win-b6bdcc569-tpnxq, cluster kcp-upgrade-61o13v/kcp-upgrade-xcxahy: [running command "get-eventlog -LogName Application -Source Docker | Select-Object Index, TimeGenerated, EntryType, Message | Sort-Object Index | Format-Table -Wrap -Autosize": Process exited with status 1, running command "docker ps -a": Process exited with status 1]
STEP: Dumping workload cluster kcp-upgrade-61o13v/kcp-upgrade-xcxahy kube-system pod logs
STEP: Fetching kube-system pod logs took 335.341277ms
STEP: Dumping workload cluster kcp-upgrade-61o13v/kcp-upgrade-xcxahy Azure activity log
STEP: Creating log watcher for controller kube-system/calico-node-windows-lv22v, container calico-node-startup
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-wdz5s, container kube-proxy
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-c4xnc, container coredns
... skipping 20 lines ...
STEP: Creating log watcher for controller kube-system/calico-node-c7q59, container calico-node
STEP: Creating log watcher for controller kube-system/kube-scheduler-kcp-upgrade-xcxahy-control-plane-nqmnn, container kube-scheduler
STEP: Creating log watcher for controller kube-system/calico-node-windows-lv22v, container calico-node-felix
STEP: Creating log watcher for controller kube-system/calico-node-4rh5l, container calico-node
STEP: Creating log watcher for controller kube-system/etcd-kcp-upgrade-xcxahy-control-plane-hppjq, container etcd
STEP: Creating log watcher for controller kube-system/etcd-kcp-upgrade-xcxahy-control-plane-hj9s6, container etcd
STEP: Got error while iterating over activity logs for resource group capz-e2e-sxin4a: insights.ActivityLogsClient#listNextResults: Failure sending next results request: StatusCode=500 -- Original Error: context deadline exceeded
STEP: Fetching activity logs took 30.000367988s
STEP: Dumping all the Cluster API resources in the "kcp-upgrade-61o13v" namespace
STEP: Deleting cluster kcp-upgrade-61o13v/kcp-upgrade-xcxahy
STEP: Deleting cluster kcp-upgrade-xcxahy
INFO: Waiting for the Cluster kcp-upgrade-61o13v/kcp-upgrade-xcxahy to be deleted
STEP: Waiting for cluster kcp-upgrade-xcxahy to be deleted
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-c4xnc, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-pfzwr, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-kcp-upgrade-xcxahy-control-plane-hj9s6, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-kcp-upgrade-xcxahy-control-plane-nqmnn, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-kcp-upgrade-xcxahy-control-plane-nqmnn, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-8kppf, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-wdz5s, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-kcp-upgrade-xcxahy-control-plane-hj9s6, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-jm2jv, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-nqhcf, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-kcp-upgrade-xcxahy-control-plane-hppjq, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-hdcz2, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-c45zk, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-hdcz2, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-lv22v, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-lv22v, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-846b5f484d-fl66c, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-zw2vp, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-kcp-upgrade-xcxahy-control-plane-hj9s6, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-kcp-upgrade-xcxahy-control-plane-hppjq, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-kcp-upgrade-xcxahy-control-plane-hppjq, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-r4mf2, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-c7q59, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-4rh5l, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-kcp-upgrade-xcxahy-control-plane-hppjq, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-kcp-upgrade-xcxahy-control-plane-nqmnn, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-kcp-upgrade-xcxahy-control-plane-nqmnn, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-tk2c9, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-kcp-upgrade-xcxahy-control-plane-hj9s6, container etcd: http2: client connection lost
STEP: Deleting namespace used for hosting the "kcp-upgrade" test spec
INFO: Deleting namespace kcp-upgrade-61o13v
STEP: Redacting sensitive information from logs


• [SLOW TEST:2371.547 seconds]
... skipping 56 lines ...
STEP: Dumping logs from the "kcp-upgrade-ek3yr3" workload cluster
STEP: Dumping workload cluster kcp-upgrade-bfluwa/kcp-upgrade-ek3yr3 logs
Nov  1 15:53:33.630: INFO: INFO: Collecting logs for node kcp-upgrade-ek3yr3-control-plane-vb2nf in cluster kcp-upgrade-ek3yr3 in namespace kcp-upgrade-bfluwa

Nov  1 15:55:44.793: INFO: INFO: Collecting boot logs for AzureMachine kcp-upgrade-ek3yr3-control-plane-vb2nf

Failed to get logs for machine kcp-upgrade-ek3yr3-control-plane-kdz78, cluster kcp-upgrade-bfluwa/kcp-upgrade-ek3yr3: dialing public load balancer at kcp-upgrade-ek3yr3-7b48aafc.eastus.cloudapp.azure.com: dial tcp 20.81.68.231:22: connect: connection timed out
Nov  1 15:55:45.663: INFO: INFO: Collecting logs for node kcp-upgrade-ek3yr3-md-0-9flld in cluster kcp-upgrade-ek3yr3 in namespace kcp-upgrade-bfluwa

Nov  1 15:57:55.869: INFO: INFO: Collecting boot logs for AzureMachine kcp-upgrade-ek3yr3-md-0-9flld

Failed to get logs for machine kcp-upgrade-ek3yr3-md-0-6d8d866668-nrj7z, cluster kcp-upgrade-bfluwa/kcp-upgrade-ek3yr3: dialing public load balancer at kcp-upgrade-ek3yr3-7b48aafc.eastus.cloudapp.azure.com: dial tcp 20.81.68.231:22: connect: connection timed out
Nov  1 15:57:56.671: INFO: INFO: Collecting logs for node 10.1.0.4 in cluster kcp-upgrade-ek3yr3 in namespace kcp-upgrade-bfluwa

Nov  1 16:04:29.085: INFO: INFO: Collecting boot logs for AzureMachine kcp-upgrade-ek3yr3-md-win-4zwvg

Failed to get logs for machine kcp-upgrade-ek3yr3-md-win-7784f44dc-4h9j6, cluster kcp-upgrade-bfluwa/kcp-upgrade-ek3yr3: dialing public load balancer at kcp-upgrade-ek3yr3-7b48aafc.eastus.cloudapp.azure.com: dial tcp 20.81.68.231:22: connect: connection timed out
Nov  1 16:04:29.956: INFO: INFO: Collecting logs for node 10.1.0.6 in cluster kcp-upgrade-ek3yr3 in namespace kcp-upgrade-bfluwa

Nov  1 16:11:02.297: INFO: INFO: Collecting boot logs for AzureMachine kcp-upgrade-ek3yr3-md-win-ns54q

Failed to get logs for machine kcp-upgrade-ek3yr3-md-win-7784f44dc-vlghq, cluster kcp-upgrade-bfluwa/kcp-upgrade-ek3yr3: dialing public load balancer at kcp-upgrade-ek3yr3-7b48aafc.eastus.cloudapp.azure.com: dial tcp 20.81.68.231:22: connect: connection timed out
STEP: Dumping workload cluster kcp-upgrade-bfluwa/kcp-upgrade-ek3yr3 kube-system pod logs
STEP: Fetching kube-system pod logs took 391.216479ms
STEP: Dumping workload cluster kcp-upgrade-bfluwa/kcp-upgrade-ek3yr3 Azure activity log
STEP: Creating log watcher for controller kube-system/calico-node-windows-k9j7q, container calico-node-felix
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-846b5f484d-dwhg5, container calico-kube-controllers
STEP: Creating log watcher for controller kube-system/kube-apiserver-kcp-upgrade-ek3yr3-control-plane-vb2nf, container kube-apiserver
... skipping 8 lines ...
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-l8576, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-pm4k6, container kube-proxy
STEP: Creating log watcher for controller kube-system/calico-node-rpf8l, container calico-node
STEP: Creating log watcher for controller kube-system/calico-node-windows-k9j7q, container calico-node-startup
STEP: Creating log watcher for controller kube-system/kube-scheduler-kcp-upgrade-ek3yr3-control-plane-vb2nf, container kube-scheduler
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-snbqq, container coredns
STEP: Got error while iterating over activity logs for resource group capz-e2e-nbb61q: insights.ActivityLogsClient#listNextResults: Failure sending next results request: StatusCode=500 -- Original Error: context deadline exceeded
STEP: Fetching activity logs took 30.000560249s
STEP: Dumping all the Cluster API resources in the "kcp-upgrade-bfluwa" namespace
STEP: Deleting cluster kcp-upgrade-bfluwa/kcp-upgrade-ek3yr3
STEP: Deleting cluster kcp-upgrade-ek3yr3
INFO: Waiting for the Cluster kcp-upgrade-bfluwa/kcp-upgrade-ek3yr3 to be deleted
STEP: Waiting for cluster kcp-upgrade-ek3yr3 to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-kcp-upgrade-ek3yr3-control-plane-vb2nf, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-pm4k6, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-kfgmx, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-l8576, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-846b5f484d-dwhg5, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-kcp-upgrade-ek3yr3-control-plane-vb2nf, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-49cwq, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-kfgmx, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-k9j7q, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-5mqlt, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-tkk8b, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-k9j7q, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-kcp-upgrade-ek3yr3-control-plane-vb2nf, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-snbqq, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-c5nbw, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-rpf8l, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-kcp-upgrade-ek3yr3-control-plane-vb2nf, container kube-controller-manager: http2: client connection lost
STEP: Deleting namespace used for hosting the "kcp-upgrade" test spec
INFO: Deleting namespace kcp-upgrade-bfluwa
STEP: Redacting sensitive information from logs


• [SLOW TEST:2552.867 seconds]
... skipping 91 lines ...
STEP: Creating log watcher for controller kube-system/calico-node-wdzbp, container calico-node
STEP: Creating log watcher for controller kube-system/kube-scheduler-kcp-upgrade-1p44az-control-plane-zjkll, container kube-scheduler
STEP: Creating log watcher for controller kube-system/kube-apiserver-kcp-upgrade-1p44az-control-plane-qhd4h, container kube-apiserver
STEP: Creating log watcher for controller kube-system/kube-scheduler-kcp-upgrade-1p44az-control-plane-wpdxl, container kube-scheduler
STEP: Creating log watcher for controller kube-system/calico-node-hzdpf, container calico-node
STEP: Creating log watcher for controller kube-system/kube-controller-manager-kcp-upgrade-1p44az-control-plane-zjkll, container kube-controller-manager
STEP: Got error while iterating over activity logs for resource group capz-e2e-uxni7k: insights.ActivityLogsClient#listNextResults: Failure sending next results request: StatusCode=500 -- Original Error: context deadline exceeded
STEP: Fetching activity logs took 30.000469851s
STEP: Dumping all the Cluster API resources in the "kcp-upgrade-pd64k3" namespace
STEP: Deleting cluster kcp-upgrade-pd64k3/kcp-upgrade-1p44az
STEP: Deleting cluster kcp-upgrade-1p44az
INFO: Waiting for the Cluster kcp-upgrade-pd64k3/kcp-upgrade-1p44az to be deleted
STEP: Waiting for cluster kcp-upgrade-1p44az to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-proxy-6jmgt, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-kcp-upgrade-1p44az-control-plane-qhd4h, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-kcp-upgrade-1p44az-control-plane-wpdxl, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-kcp-upgrade-1p44az-control-plane-zjkll, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-p549c, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-jrgxc, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-kcp-upgrade-1p44az-control-plane-wpdxl, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-dqc2f, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-kcp-upgrade-1p44az-control-plane-qhd4h, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-kcp-upgrade-1p44az-control-plane-zjkll, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-lwgnp, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-kcp-upgrade-1p44az-control-plane-zjkll, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-kcp-upgrade-1p44az-control-plane-qhd4h, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-kcp-upgrade-1p44az-control-plane-wpdxl, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-kcp-upgrade-1p44az-control-plane-wpdxl, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-hzdpf, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-wdzbp, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-lqgzm, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-bl5z9, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-846b5f484d-2kx2s, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-kcp-upgrade-1p44az-control-plane-zjkll, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-s8fk6, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-kcp-upgrade-1p44az-control-plane-qhd4h, container kube-apiserver: http2: client connection lost
STEP: Deleting namespace used for hosting the "kcp-upgrade" test spec
INFO: Deleting namespace kcp-upgrade-pd64k3
STEP: Redacting sensitive information from logs


• [SLOW TEST:2233.738 seconds]
... skipping 7 lines ...
Running the Cluster API E2E tests Running the self-hosted spec 
  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

STEP: Creating namespace "self-hosted" for hosting the cluster
Nov  1 16:19:22.437: INFO: starting to create namespace for hosting the "self-hosted" test spec
2021/11/01 16:19:22 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-euz426" using the "management" template (Kubernetes v1.22.1, 1 control-plane machines, 1 worker machines)
INFO: Getting the cluster template yaml
INFO: clusterctl config cluster self-hosted-euz426 --infrastructure (default) --kubernetes-version v1.22.1 --control-plane-machine-count 1 --worker-machine-count 1 --flavor management
... skipping 73 lines ...
STEP: Fetching activity logs took 496.109987ms
STEP: Dumping all the Cluster API resources in the "self-hosted" namespace
STEP: Deleting all clusters in the self-hosted namespace
STEP: Deleting cluster self-hosted-euz426
INFO: Waiting for the Cluster self-hosted/self-hosted-euz426 to be deleted
STEP: Waiting for cluster self-hosted-euz426 to be deleted
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-846b5f484d-8b2m5, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-self-hosted-euz426-control-plane-t6mmz, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-z5qxh, container coredns: http2: client connection lost
INFO: Got error while streaming logs for pod capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager-865c969d7-jbkgq, container manager: http2: client connection lost
INFO: Got error while streaming logs for pod capz-system/capz-controller-manager-74bf9c9764-9fr6n, container manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-4n849, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-q55r2, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-mpqz7, container kube-proxy: http2: client connection lost
INFO: Got error while streaming logs for pod capi-system/capi-controller-manager-6bdc78c4d4-5rsfg, container manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-self-hosted-euz426-control-plane-t6mmz, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-c2zrt, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-self-hosted-euz426-control-plane-t6mmz, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-5zkdg, container calico-node: http2: client connection lost
INFO: Got error while streaming logs for pod capi-kubeadm-control-plane-system/capi-kubeadm-control-plane-controller-manager-86b5f554dd-8hm8x, container manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-self-hosted-euz426-control-plane-t6mmz, container kube-controller-manager: http2: client connection lost
STEP: Deleting namespace used for hosting the "self-hosted" test spec
INFO: Deleting namespace self-hosted
STEP: Checking if any resources are left over in Azure for spec "self-hosted"
STEP: Redacting sensitive information from logs
STEP: Redacting sensitive information from logs

... skipping 10 lines ...