This job view page is being replaced by Spyglass soon. Check out the new job view.
Resultfailure
Tests 0 failed / 4 succeeded
Started2022-09-05 20:28
Elapsed4h15m
Revision
uploadercrier
uploadercrier

No Test Failures!


Show 4 Passed Tests

Show 10 Skipped Tests

Error lines from build-log.txt

... skipping 531 lines ...
 ✓ Installing CNI 🔌
 • Installing StorageClass 💾  ...
 ✓ Installing StorageClass 💾
INFO: The kubeconfig file for the kind cluster is /tmp/e2e-kind3551854432
INFO: Loading image: "capzci.azurecr.io/cluster-api-azure-controller-amd64:20220905202951"
INFO: Loading image: "registry.k8s.io/cluster-api/cluster-api-controller:v1.1.4"
INFO: [WARNING] Unable to load image "registry.k8s.io/cluster-api/cluster-api-controller:v1.1.4" into the kind cluster "capz-e2e": error saving image "registry.k8s.io/cluster-api/cluster-api-controller:v1.1.4" to "/tmp/image-tar479618068/image.tar": unable to read image data: Error response from daemon: reference does not exist
INFO: Loading image: "registry.k8s.io/cluster-api/kubeadm-bootstrap-controller:v1.1.4"
INFO: [WARNING] Unable to load image "registry.k8s.io/cluster-api/kubeadm-bootstrap-controller:v1.1.4" into the kind cluster "capz-e2e": error saving image "registry.k8s.io/cluster-api/kubeadm-bootstrap-controller:v1.1.4" to "/tmp/image-tar3781745419/image.tar": unable to read image data: Error response from daemon: reference does not exist
INFO: Loading image: "registry.k8s.io/cluster-api/kubeadm-control-plane-controller:v1.1.4"
INFO: [WARNING] Unable to load image "registry.k8s.io/cluster-api/kubeadm-control-plane-controller:v1.1.4" into the kind cluster "capz-e2e": error saving image "registry.k8s.io/cluster-api/kubeadm-control-plane-controller:v1.1.4" to "/tmp/image-tar2980595047/image.tar": unable to read image data: Error response from daemon: reference does not exist
STEP: Initializing the bootstrap cluster
INFO: clusterctl init --core cluster-api --bootstrap kubeadm --control-plane kubeadm --infrastructure azure
INFO: Waiting for provider controllers to be running
STEP: Waiting for deployment capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager to be available
INFO: Creating log watcher for controller capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager, pod capi-kubeadm-bootstrap-controller-manager-8447dbccc5-mq4qn, container manager
STEP: Waiting for deployment capi-kubeadm-control-plane-system/capi-kubeadm-control-plane-controller-manager to be available
... skipping 12 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:108

STEP: Creating namespace "self-hosted" for hosting the cluster
Sep  5 20:41:09.831: INFO: starting to create namespace for hosting the "self-hosted" test spec
2022/09/05 20:41:09 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-7ofs1p" using the "management" template (Kubernetes v1.22.13, 1 control-plane machines, 1 worker machines)
INFO: Getting the cluster template yaml
INFO: clusterctl config cluster self-hosted-7ofs1p --infrastructure (default) --kubernetes-version v1.22.13 --control-plane-machine-count 1 --worker-machine-count 1 --flavor management
... skipping 63 lines ...
STEP: Collecting events for Pod kube-system/etcd-self-hosted-7ofs1p-control-plane-pzj5k
STEP: Creating log watcher for controller kube-system/calico-node-p44vl, container calico-node
STEP: Collecting events for Pod kube-system/kube-apiserver-self-hosted-7ofs1p-control-plane-pzj5k
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-5kd4c, container coredns
STEP: Creating log watcher for controller kube-system/calico-node-tdxzk, container calico-node
STEP: Creating log watcher for controller kube-system/kube-controller-manager-self-hosted-7ofs1p-control-plane-pzj5k, container kube-controller-manager
STEP: failed to find events of Pod "kube-apiserver-self-hosted-7ofs1p-control-plane-pzj5k"
STEP: Collecting events for Pod kube-system/calico-node-tdxzk
STEP: Collecting events for Pod kube-system/calico-node-p44vl
STEP: Creating log watcher for controller kube-system/kube-proxy-kt6f2, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-zwzcw
STEP: Collecting events for Pod kube-system/kube-proxy-kt6f2
STEP: Creating log watcher for controller kube-system/kube-proxy-zwzcw, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-scheduler-self-hosted-7ofs1p-control-plane-pzj5k
STEP: Creating log watcher for controller kube-system/kube-scheduler-self-hosted-7ofs1p-control-plane-pzj5k, container kube-scheduler
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-rjmhb, container coredns
STEP: failed to find events of Pod "kube-scheduler-self-hosted-7ofs1p-control-plane-pzj5k"
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-5kd4c
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-rjmhb
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-nnfwk
STEP: Creating log watcher for controller kube-system/etcd-self-hosted-7ofs1p-control-plane-pzj5k, container etcd
STEP: Creating log watcher for controller kube-system/kube-apiserver-self-hosted-7ofs1p-control-plane-pzj5k, container kube-apiserver
STEP: failed to find events of Pod "etcd-self-hosted-7ofs1p-control-plane-pzj5k"
STEP: failed to find events of Pod "kube-controller-manager-self-hosted-7ofs1p-control-plane-pzj5k"
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-nnfwk, container calico-kube-controllers
STEP: Fetching activity logs took 1.963693583s
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-7ofs1p
INFO: Waiting for the Cluster self-hosted/self-hosted-7ofs1p to be deleted
... skipping 68 lines ...
Sep  5 20:50:01.980: INFO: Collecting boot logs for AzureMachine quick-start-0pgouo-md-0-22zhg

Sep  5 20:50:02.518: INFO: Collecting logs for Windows node quick-sta-thrch in cluster quick-start-0pgouo in namespace quick-start-ysbf4c

Sep  5 20:51:31.637: INFO: Collecting boot logs for AzureMachine quick-start-0pgouo-md-win-thrch

Failed to get logs for machine quick-start-0pgouo-md-win-55f965c6f8-bqtt8, cluster quick-start-ysbf4c/quick-start-0pgouo: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Sep  5 20:51:32.392: INFO: Collecting logs for Windows node quick-sta-982zd in cluster quick-start-0pgouo in namespace quick-start-ysbf4c

Sep  5 20:53:04.580: INFO: Collecting boot logs for AzureMachine quick-start-0pgouo-md-win-982zd

Failed to get logs for machine quick-start-0pgouo-md-win-55f965c6f8-wgkmh, cluster quick-start-ysbf4c/quick-start-0pgouo: running command "Get-Content "C:\\cni.log"": Process exited with status 1
STEP: Dumping workload cluster quick-start-ysbf4c/quick-start-0pgouo kube-system pod logs
STEP: Fetching kube-system pod logs took 1.128894526s
STEP: Creating log watcher for controller kube-system/calico-node-windows-fnzm6, container calico-node-startup
STEP: Creating log watcher for controller kube-system/kube-controller-manager-quick-start-0pgouo-control-plane-vxg99, container kube-controller-manager
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-wvhd2
STEP: Collecting events for Pod kube-system/calico-node-xbzcb
STEP: Collecting events for Pod kube-system/kube-controller-manager-quick-start-0pgouo-control-plane-vxg99
STEP: Creating log watcher for controller kube-system/kube-apiserver-quick-start-0pgouo-control-plane-vxg99, container kube-apiserver
STEP: failed to find events of Pod "kube-controller-manager-quick-start-0pgouo-control-plane-vxg99"
STEP: Creating log watcher for controller kube-system/kube-proxy-7sn8p, container kube-proxy
STEP: Creating log watcher for controller kube-system/calico-node-xxqvz, container calico-node
STEP: Collecting events for Pod kube-system/containerd-logger-jtxrl
STEP: Collecting events for Pod kube-system/kube-proxy-7sn8p
STEP: Creating log watcher for controller kube-system/kube-proxy-jj5qz, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-apiserver-quick-start-0pgouo-control-plane-vxg99
STEP: failed to find events of Pod "kube-apiserver-quick-start-0pgouo-control-plane-vxg99"
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-wfz6b, container coredns
STEP: Collecting events for Pod kube-system/calico-node-xxqvz
STEP: Collecting events for Pod kube-system/etcd-quick-start-0pgouo-control-plane-vxg99
STEP: Creating log watcher for controller kube-system/containerd-logger-js5jt, container containerd-logger
STEP: failed to find events of Pod "etcd-quick-start-0pgouo-control-plane-vxg99"
STEP: Creating log watcher for controller kube-system/csi-proxy-hjl8k, container csi-proxy
STEP: Collecting events for Pod kube-system/containerd-logger-js5jt
STEP: Collecting events for Pod kube-system/csi-proxy-hjl8k
STEP: Creating log watcher for controller kube-system/containerd-logger-jtxrl, container containerd-logger
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-kdk8q
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-kdk8q, container calico-kube-controllers
... skipping 10 lines ...
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-zhkkn, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-windows-zhkkn
STEP: Creating log watcher for controller kube-system/kube-scheduler-quick-start-0pgouo-control-plane-vxg99, container kube-scheduler
STEP: Collecting events for Pod kube-system/calico-node-windows-fnzm6
STEP: Collecting events for Pod kube-system/kube-scheduler-quick-start-0pgouo-control-plane-vxg99
STEP: Creating log watcher for controller kube-system/calico-node-xbzcb, container calico-node
STEP: failed to find events of Pod "kube-scheduler-quick-start-0pgouo-control-plane-vxg99"
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-wfz6b
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-wvhd2, container coredns
STEP: Creating log watcher for controller kube-system/calico-node-windows-2hlrr, container calico-node-startup
STEP: Fetching activity logs took 1.348893757s
STEP: Dumping all the Cluster API resources in the "quick-start-ysbf4c" namespace
STEP: Deleting cluster quick-start-ysbf4c/quick-start-0pgouo
STEP: Deleting cluster quick-start-0pgouo
INFO: Waiting for the Cluster quick-start-ysbf4c/quick-start-0pgouo to be deleted
STEP: Waiting for cluster quick-start-0pgouo to be deleted
STEP: Got error while streaming logs for pod kube-system/containerd-logger-js5jt, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-5nz62, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-hjl8k, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-jtxrl, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-fnzm6, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-2hlrr, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-zhkkn, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-fnzm6, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-q7fvp, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-2hlrr, container calico-node-felix: http2: client connection lost
STEP: Deleting namespace used for hosting the "quick-start" test spec
INFO: Deleting namespace quick-start-ysbf4c
STEP: Redacting sensitive information from logs


• [SLOW TEST:1166.627 seconds]
... skipping 85 lines ...
STEP: Fetching activity logs took 1.84001924s
STEP: Dumping all the Cluster API resources in the "mhc-remediation-isrxff" namespace
STEP: Deleting cluster mhc-remediation-isrxff/mhc-remediation-zoqrlu
STEP: Deleting cluster mhc-remediation-zoqrlu
INFO: Waiting for the Cluster mhc-remediation-isrxff/mhc-remediation-zoqrlu to be deleted
STEP: Waiting for cluster mhc-remediation-zoqrlu to be deleted
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-9c624, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-mhc-remediation-zoqrlu-control-plane-fpsfv, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-mhc-remediation-zoqrlu-control-plane-fpsfv, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-gm8wv, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-mhc-remediation-zoqrlu-control-plane-fpsfv, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-2tmg6, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-9hns4, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-nhd7q, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-zvdg9, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-x2kvl, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-mhc-remediation-zoqrlu-control-plane-fpsfv, container kube-apiserver: http2: client connection lost
STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
INFO: Deleting namespace mhc-remediation-isrxff
STEP: Redacting sensitive information from logs


• [SLOW TEST:1120.864 seconds]
... skipping 119 lines ...
STEP: Fetching activity logs took 3.508997006s
STEP: Dumping all the Cluster API resources in the "mhc-remediation-7iokjf" namespace
STEP: Deleting cluster mhc-remediation-7iokjf/mhc-remediation-amzzj8
STEP: Deleting cluster mhc-remediation-amzzj8
INFO: Waiting for the Cluster mhc-remediation-7iokjf/mhc-remediation-amzzj8 to be deleted
STEP: Waiting for cluster mhc-remediation-amzzj8 to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-mhc-remediation-amzzj8-control-plane-297cg, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-mhc-remediation-amzzj8-control-plane-297cg, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-mhc-remediation-amzzj8-control-plane-297cg, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-4fnln, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-mmj59, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-mhc-remediation-amzzj8-control-plane-297cg, container kube-controller-manager: http2: client connection lost
STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
INFO: Deleting namespace mhc-remediation-7iokjf
STEP: Redacting sensitive information from logs


• [SLOW TEST:1297.557 seconds]
... skipping 50 lines ...
STEP: Creating log watcher for controller kube-system/kube-scheduler-kcp-adoption-tzakvc-control-plane-0, container kube-scheduler
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-n52nh, container coredns
STEP: Creating log watcher for controller kube-system/etcd-kcp-adoption-tzakvc-control-plane-0, container etcd
STEP: Collecting events for Pod kube-system/etcd-kcp-adoption-tzakvc-control-plane-0
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-n52nh
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-gsgcb, container coredns
STEP: failed to find events of Pod "etcd-kcp-adoption-tzakvc-control-plane-0"
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-gsgcb
STEP: Fetching kube-system pod logs took 757.48003ms
STEP: Dumping workload cluster kcp-adoption-ms5jz2/kcp-adoption-tzakvc Azure activity log
STEP: failed to find events of Pod "kube-controller-manager-kcp-adoption-tzakvc-control-plane-0"
STEP: Collecting events for Pod kube-system/kube-scheduler-kcp-adoption-tzakvc-control-plane-0
STEP: failed to find events of Pod "kube-scheduler-kcp-adoption-tzakvc-control-plane-0"
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-8xvc5
STEP: Creating log watcher for controller kube-system/calico-node-5jchj, container calico-node
STEP: Collecting events for Pod kube-system/kube-proxy-q86f8
STEP: Collecting events for Pod kube-system/calico-node-5jchj
STEP: Collecting events for Pod kube-system/kube-apiserver-kcp-adoption-tzakvc-control-plane-0
STEP: Creating log watcher for controller kube-system/kube-proxy-q86f8, container kube-proxy
STEP: failed to find events of Pod "kube-apiserver-kcp-adoption-tzakvc-control-plane-0"
STEP: Creating log watcher for controller kube-system/kube-controller-manager-kcp-adoption-tzakvc-control-plane-0, container kube-controller-manager
STEP: Fetching activity logs took 839.342591ms
STEP: Dumping all the Cluster API resources in the "kcp-adoption-ms5jz2" namespace
STEP: Deleting cluster kcp-adoption-ms5jz2/kcp-adoption-tzakvc
STEP: Deleting cluster kcp-adoption-tzakvc
INFO: Waiting for the Cluster kcp-adoption-ms5jz2/kcp-adoption-tzakvc to be deleted
... skipping 106 lines ...
STEP: Creating log watcher for controller kube-system/kube-apiserver-machine-pool-5qja3a-control-plane-6pvmc, container kube-apiserver
STEP: Creating log watcher for controller kube-system/kube-proxy-kzsss, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-dhvb9, container kube-proxy
STEP: Dumping workload cluster machine-pool-kfj53f/machine-pool-5qja3a Azure activity log
STEP: Creating log watcher for controller kube-system/calico-node-krcgx, container calico-node
STEP: Creating log watcher for controller kube-system/calico-node-windows-ftkdq, container calico-node-felix
STEP: Error starting logs stream for pod kube-system/calico-node-d89xn, container calico-node: pods "machine-pool-5qja3a-mp-0000001" not found
STEP: Error starting logs stream for pod kube-system/calico-node-windows-ftkdq, container calico-node-startup: pods "win-p-win000002" not found
STEP: Error starting logs stream for pod kube-system/kube-proxy-cp965, container kube-proxy: pods "machine-pool-5qja3a-mp-0000001" not found
STEP: Error starting logs stream for pod kube-system/kube-proxy-windows-dhvb9, container kube-proxy: pods "win-p-win000002" not found
STEP: Error starting logs stream for pod kube-system/calico-node-windows-ftkdq, container calico-node-felix: pods "win-p-win000002" not found
STEP: Fetching activity logs took 1.552135917s
STEP: Dumping all the Cluster API resources in the "machine-pool-kfj53f" namespace
STEP: Deleting cluster machine-pool-kfj53f/machine-pool-5qja3a
STEP: Deleting cluster machine-pool-5qja3a
INFO: Waiting for the Cluster machine-pool-kfj53f/machine-pool-5qja3a to be deleted
STEP: Waiting for cluster machine-pool-5qja3a to be deleted
STEP: Error starting logs stream for pod kube-system/kube-proxy-5pn97, container kube-proxy: Get "https://10.1.0.8:10250/containerLogs/kube-system/kube-proxy-5pn97/kube-proxy?follow=true": dial tcp 10.1.0.8:10250: i/o timeout
STEP: Error starting logs stream for pod kube-system/kube-proxy-kzsss, container kube-proxy: Get "https://10.1.0.4:10250/containerLogs/kube-system/kube-proxy-kzsss/kube-proxy?follow=true": dial tcp 10.1.0.4:10250: i/o timeout
STEP: Error starting logs stream for pod kube-system/calico-node-84wpf, container calico-node: Get "https://10.1.0.8:10250/containerLogs/kube-system/calico-node-84wpf/calico-node?follow=true": dial tcp 10.1.0.8:10250: i/o timeout
STEP: Error starting logs stream for pod kube-system/calico-node-t9b7l, container calico-node: Get "https://10.1.0.4:10250/containerLogs/kube-system/calico-node-t9b7l/calico-node?follow=true": dial tcp 10.1.0.4:10250: i/o timeout
STEP: Got error while streaming logs for pod kube-system/kube-proxy-5fbzb, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-thb2w, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-machine-pool-5qja3a-control-plane-6pvmc, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-machine-pool-5qja3a-control-plane-6pvmc, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-krcgx, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-machine-pool-5qja3a-control-plane-6pvmc, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-machine-pool-5qja3a-control-plane-6pvmc, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-94wvv, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-tfzwt, container coredns: http2: client connection lost
STEP: Deleting namespace used for hosting the "machine-pool" test spec
INFO: Deleting namespace machine-pool-kfj53f
STEP: Redacting sensitive information from logs


• [SLOW TEST:1324.888 seconds]
... skipping 65 lines ...
Sep  5 21:39:58.172: INFO: Collecting boot logs for AzureMachine md-scale-xvxup5-md-0-rrpqf

Sep  5 21:39:59.118: INFO: Collecting logs for Windows node md-scale-8xx5h in cluster md-scale-xvxup5 in namespace md-scale-1pwzqr

Sep  5 21:41:30.508: INFO: Collecting boot logs for AzureMachine md-scale-xvxup5-md-win-8xx5h

Failed to get logs for machine md-scale-xvxup5-md-win-5b66464746-9x6dr, cluster md-scale-1pwzqr/md-scale-xvxup5: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Sep  5 21:41:31.689: INFO: Collecting logs for Windows node md-scale-f4hdb in cluster md-scale-xvxup5 in namespace md-scale-1pwzqr

Sep  5 21:43:03.220: INFO: Collecting boot logs for AzureMachine md-scale-xvxup5-md-win-f4hdb

Failed to get logs for machine md-scale-xvxup5-md-win-5b66464746-sbzff, cluster md-scale-1pwzqr/md-scale-xvxup5: running command "Get-Content "C:\\cni.log"": Process exited with status 1
STEP: Dumping workload cluster md-scale-1pwzqr/md-scale-xvxup5 kube-system pod logs
STEP: Collecting events for Pod kube-system/calico-node-gztlr
STEP: Creating log watcher for controller kube-system/calico-node-windows-9wbtl, container calico-node-felix
STEP: Collecting events for Pod kube-system/csi-proxy-prhdk
STEP: Collecting events for Pod kube-system/kube-proxy-windows-989s9
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-prkk7, container kube-proxy
... skipping 21 lines ...
STEP: Creating log watcher for controller kube-system/csi-proxy-prhdk, container csi-proxy
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-hhb4d, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/kube-scheduler-md-scale-xvxup5-control-plane-2ww2f
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-hhb4d
STEP: Creating log watcher for controller kube-system/kube-proxy-jwz6w, container kube-proxy
STEP: Collecting events for Pod kube-system/etcd-md-scale-xvxup5-control-plane-2ww2f
STEP: failed to find events of Pod "etcd-md-scale-xvxup5-control-plane-2ww2f"
STEP: Creating log watcher for controller kube-system/kube-apiserver-md-scale-xvxup5-control-plane-2ww2f, container kube-apiserver
STEP: Collecting events for Pod kube-system/kube-proxy-jwz6w
STEP: Collecting events for Pod kube-system/kube-apiserver-md-scale-xvxup5-control-plane-2ww2f
STEP: failed to find events of Pod "kube-apiserver-md-scale-xvxup5-control-plane-2ww2f"
STEP: Creating log watcher for controller kube-system/kube-controller-manager-md-scale-xvxup5-control-plane-2ww2f, container kube-controller-manager
STEP: Collecting events for Pod kube-system/kube-controller-manager-md-scale-xvxup5-control-plane-2ww2f
STEP: Creating log watcher for controller kube-system/kube-proxy-bqs4b, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-bqs4b
STEP: Collecting events for Pod kube-system/kube-proxy-windows-prkk7
STEP: Dumping workload cluster md-scale-1pwzqr/md-scale-xvxup5 Azure activity log
STEP: Creating log watcher for controller kube-system/calico-node-windows-fdfdb, container calico-node-startup
STEP: Fetching activity logs took 1.3670224s
STEP: Dumping all the Cluster API resources in the "md-scale-1pwzqr" namespace
STEP: Deleting cluster md-scale-1pwzqr/md-scale-xvxup5
STEP: Deleting cluster md-scale-xvxup5
INFO: Waiting for the Cluster md-scale-1pwzqr/md-scale-xvxup5 to be deleted
STEP: Waiting for cluster md-scale-xvxup5 to be deleted
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-9wbtl, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-7lbpv, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-s9jzn, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-hhb4d, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-9wbtl, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-gztlr, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-prkk7, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-sdrrp, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-jwz6w, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-4sj55, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-md-scale-xvxup5-control-plane-2ww2f, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-989s9, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-bgvmx, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-fdfdb, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-md-scale-xvxup5-control-plane-2ww2f, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-md-scale-xvxup5-control-plane-2ww2f, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-bqs4b, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-q4fwx, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-fdfdb, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-md-scale-xvxup5-control-plane-2ww2f, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-prhdk, container csi-proxy: http2: client connection lost
STEP: Deleting namespace used for hosting the "md-scale" test spec
INFO: Deleting namespace md-scale-1pwzqr
STEP: Redacting sensitive information from logs


• [SLOW TEST:1211.770 seconds]
... skipping 58 lines ...
STEP: Dumping logs from the "node-drain-zm1uu4" workload cluster
STEP: Dumping workload cluster node-drain-2scx8e/node-drain-zm1uu4 logs
Sep  5 22:02:15.563: INFO: Collecting logs for Linux node node-drain-zm1uu4-control-plane-92xg7 in cluster node-drain-zm1uu4 in namespace node-drain-2scx8e

Sep  5 22:08:49.112: INFO: Collecting boot logs for AzureMachine node-drain-zm1uu4-control-plane-92xg7

Failed to get logs for machine node-drain-zm1uu4-control-plane-vflvz, cluster node-drain-2scx8e/node-drain-zm1uu4: dialing public load balancer at node-drain-zm1uu4-23402f52.uksouth.cloudapp.azure.com: dial tcp 20.26.160.212:22: connect: connection timed out
STEP: Dumping workload cluster node-drain-2scx8e/node-drain-zm1uu4 kube-system pod logs
STEP: Fetching kube-system pod logs took 1.056604602s
STEP: Dumping workload cluster node-drain-2scx8e/node-drain-zm1uu4 Azure activity log
STEP: Creating log watcher for controller kube-system/etcd-node-drain-zm1uu4-control-plane-92xg7, container etcd
STEP: Collecting events for Pod kube-system/calico-node-bzqzk
STEP: Creating log watcher for controller kube-system/kube-controller-manager-node-drain-zm1uu4-control-plane-92xg7, container kube-controller-manager
... skipping 15 lines ...
STEP: Fetching activity logs took 2.712512158s
STEP: Dumping all the Cluster API resources in the "node-drain-2scx8e" namespace
STEP: Deleting cluster node-drain-2scx8e/node-drain-zm1uu4
STEP: Deleting cluster node-drain-zm1uu4
INFO: Waiting for the Cluster node-drain-2scx8e/node-drain-zm1uu4 to be deleted
STEP: Waiting for cluster node-drain-zm1uu4 to be deleted
STEP: Got error while streaming logs for pod kube-system/etcd-node-drain-zm1uu4-control-plane-92xg7, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-cwv42, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-tbmm8, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-node-drain-zm1uu4-control-plane-92xg7, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-node-drain-zm1uu4-control-plane-92xg7, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-4cz4c, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-node-drain-zm1uu4-control-plane-92xg7, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-bzqzk, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-m5ss7, container coredns: http2: client connection lost
STEP: Deleting namespace used for hosting the "node-drain" test spec
INFO: Deleting namespace node-drain-2scx8e
STEP: Redacting sensitive information from logs


• [SLOW TEST:1813.672 seconds]
Running the Cluster API E2E tests
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/capi_test.go:44
  Should successfully set and use node drain timeout
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/capi_test.go:188
    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.1.4/e2e/node_drain_timeout.go:82
------------------------------
{"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-06T00:29:07Z"}
++ 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: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-06T00:44:08Z"}
{"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-06T00:44:08Z"}