This job view page is being replaced by Spyglass soon. Check out the new job view.
Resultsuccess
Tests 0 failed / 9 succeeded
Started2022-09-04 20:28
Elapsed1h32m
Revision
uploadercrier
uploadercrier

No Test Failures!


Show 9 Passed Tests

Show 14 Skipped Tests

Error lines from build-log.txt

... skipping 526 lines ...
 ✓ Installing CNI 🔌
 • Installing StorageClass 💾  ...
 ✓ Installing StorageClass 💾
INFO: The kubeconfig file for the kind cluster is /tmp/e2e-kind1918970748
INFO: Loading image: "capzci.azurecr.io/cluster-api-azure-controller-amd64:20220904202917"
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-tar1090986338/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-tar3259303853/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-tar2070095037/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-z6sg6, container manager
STEP: Waiting for deployment capi-kubeadm-control-plane-system/capi-kubeadm-control-plane-controller-manager to be available
... skipping 19 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  4 20:37:54.493: INFO: starting to create namespace for hosting the "self-hosted" test spec
2022/09/04 20:37:54 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-8w9117" 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-8w9117 --infrastructure (default) --kubernetes-version v1.22.13 --control-plane-machine-count 1 --worker-machine-count 1 --flavor management
... skipping 63 lines ...
STEP: Creating log watcher for controller kube-system/kube-controller-manager-self-hosted-8w9117-control-plane-xs2jz, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/kube-proxy-58xvh, container kube-proxy
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-fxlzn, container calico-kube-controllers
STEP: Creating log watcher for controller kube-system/calico-node-rt88p, container calico-node
STEP: Collecting events for Pod kube-system/etcd-self-hosted-8w9117-control-plane-xs2jz
STEP: Creating log watcher for controller kube-system/calico-node-6cxss, container calico-node
STEP: failed to find events of Pod "etcd-self-hosted-8w9117-control-plane-xs2jz"
STEP: Collecting events for Pod kube-system/calico-node-rt88p
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-qnqn4
STEP: Dumping workload cluster self-hosted/self-hosted-8w9117 Azure activity log
STEP: Creating log watcher for controller kube-system/etcd-self-hosted-8w9117-control-plane-xs2jz, container etcd
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-qnqn4, container coredns
STEP: Collecting events for Pod kube-system/kube-scheduler-self-hosted-8w9117-control-plane-xs2jz
STEP: Creating log watcher for controller kube-system/kube-apiserver-self-hosted-8w9117-control-plane-xs2jz, container kube-apiserver
STEP: failed to find events of Pod "kube-scheduler-self-hosted-8w9117-control-plane-xs2jz"
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-2xcf2, container coredns
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-2xcf2
STEP: Collecting events for Pod kube-system/kube-apiserver-self-hosted-8w9117-control-plane-xs2jz
STEP: failed to find events of Pod "kube-apiserver-self-hosted-8w9117-control-plane-xs2jz"
STEP: Collecting events for Pod kube-system/kube-proxy-8s8mg
STEP: Collecting events for Pod kube-system/kube-proxy-58xvh
STEP: Creating log watcher for controller kube-system/kube-proxy-8s8mg, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-controller-manager-self-hosted-8w9117-control-plane-xs2jz
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-fxlzn
STEP: failed to find events of Pod "kube-controller-manager-self-hosted-8w9117-control-plane-xs2jz"
STEP: Fetching activity logs took 1.205597076s
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-8w9117
INFO: Waiting for the Cluster self-hosted/self-hosted-8w9117 to be deleted
STEP: Waiting for cluster self-hosted-8w9117 to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-self-hosted-8w9117-control-plane-xs2jz, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-2xcf2, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-self-hosted-8w9117-control-plane-xs2jz, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-qnqn4, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-fxlzn, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-self-hosted-8w9117-control-plane-xs2jz, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-rt88p, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-58xvh, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-self-hosted-8w9117-control-plane-xs2jz, 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 61 lines ...
Sep  4 20:55:38.955: INFO: Collecting boot logs for AzureMachine quick-start-9okskz-md-0-qf4jb

Sep  4 20:55:39.481: INFO: Collecting logs for Windows node quick-sta-fmxh2 in cluster quick-start-9okskz in namespace quick-start-6xxjaa

Sep  4 20:57:06.760: INFO: Collecting boot logs for AzureMachine quick-start-9okskz-md-win-fmxh2

Failed to get logs for machine quick-start-9okskz-md-win-647d68f8bf-4tc2k, cluster quick-start-6xxjaa/quick-start-9okskz: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Sep  4 20:57:07.103: INFO: Collecting logs for Windows node quick-sta-j9z95 in cluster quick-start-9okskz in namespace quick-start-6xxjaa

Sep  4 20:58:34.947: INFO: Collecting boot logs for AzureMachine quick-start-9okskz-md-win-j9z95

Failed to get logs for machine quick-start-9okskz-md-win-647d68f8bf-bnsmq, cluster quick-start-6xxjaa/quick-start-9okskz: running command "Get-Content "C:\\cni.log"": Process exited with status 1
STEP: Dumping workload cluster quick-start-6xxjaa/quick-start-9okskz kube-system pod logs
STEP: Creating log watcher for controller kube-system/calico-node-windows-npz74, container calico-node-startup
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-2k7vw, container coredns
STEP: Creating log watcher for controller kube-system/calico-node-nstbl, container calico-node
STEP: Creating log watcher for controller kube-system/calico-node-windows-4zwhj, container calico-node-startup
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-lghr5
... skipping 10 lines ...
STEP: Dumping workload cluster quick-start-6xxjaa/quick-start-9okskz Azure activity log
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-2k7vw
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-kqrwr, container coredns
STEP: Collecting events for Pod kube-system/calico-node-nstbl
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-kqrwr
STEP: Collecting events for Pod kube-system/etcd-quick-start-9okskz-control-plane-5v77z
STEP: failed to find events of Pod "etcd-quick-start-9okskz-control-plane-5v77z"
STEP: Collecting events for Pod kube-system/kube-scheduler-quick-start-9okskz-control-plane-5v77z
STEP: failed to find events of Pod "kube-scheduler-quick-start-9okskz-control-plane-5v77z"
STEP: Collecting events for Pod kube-system/kube-proxy-s5bpw
STEP: Creating log watcher for controller kube-system/kube-proxy-gtdhp, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-vmqwn, container kube-proxy
STEP: Collecting events for Pod kube-system/calico-node-windows-npz74
STEP: Creating log watcher for controller kube-system/containerd-logger-fhkxq, container containerd-logger
STEP: Collecting events for Pod kube-system/containerd-logger-fhkxq
STEP: Creating log watcher for controller kube-system/containerd-logger-zrngg, container containerd-logger
STEP: Collecting events for Pod kube-system/containerd-logger-zrngg
STEP: Collecting events for Pod kube-system/csi-proxy-hq5wq
STEP: Collecting events for Pod kube-system/kube-controller-manager-quick-start-9okskz-control-plane-5v77z
STEP: failed to find events of Pod "kube-apiserver-quick-start-9okskz-control-plane-5v77z"
STEP: Collecting events for Pod kube-system/kube-proxy-gtdhp
STEP: Creating log watcher for controller kube-system/kube-apiserver-quick-start-9okskz-control-plane-5v77z, container kube-apiserver
STEP: Creating log watcher for controller kube-system/csi-proxy-cgfzk, container csi-proxy
STEP: Creating log watcher for controller kube-system/calico-node-windows-npz74, container calico-node-felix
STEP: Creating log watcher for controller kube-system/kube-scheduler-quick-start-9okskz-control-plane-5v77z, container kube-scheduler
STEP: Creating log watcher for controller kube-system/csi-proxy-hq5wq, container csi-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-windows-78vdq
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-78vdq, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-windows-vmqwn
STEP: Creating log watcher for controller kube-system/kube-proxy-s5bpw, container kube-proxy
STEP: failed to find events of Pod "kube-controller-manager-quick-start-9okskz-control-plane-5v77z"
STEP: Fetching activity logs took 1.3934732s
STEP: Dumping all the Cluster API resources in the "quick-start-6xxjaa" namespace
STEP: Deleting cluster quick-start-6xxjaa/quick-start-9okskz
STEP: Deleting cluster quick-start-9okskz
INFO: Waiting for the Cluster quick-start-6xxjaa/quick-start-9okskz to be deleted
STEP: Waiting for cluster quick-start-9okskz to be deleted
STEP: Got error while streaming logs for pod kube-system/containerd-logger-fhkxq, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-hq5wq, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-78vdq, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-npz74, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-npz74, container calico-node-startup: http2: client connection lost
STEP: Deleting namespace used for hosting the "quick-start" test spec
INFO: Deleting namespace quick-start-6xxjaa
STEP: Redacting sensitive information from logs


• [SLOW TEST:1732.630 seconds]
... skipping 85 lines ...
STEP: Fetching activity logs took 1.443310414s
STEP: Dumping all the Cluster API resources in the "mhc-remediation-zggem2" namespace
STEP: Deleting cluster mhc-remediation-zggem2/mhc-remediation-1097yo
STEP: Deleting cluster mhc-remediation-1097yo
INFO: Waiting for the Cluster mhc-remediation-zggem2/mhc-remediation-1097yo to be deleted
STEP: Waiting for cluster mhc-remediation-1097yo to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-proxy-sj994, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-kdtx7, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-bfr8w, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-mhc-remediation-1097yo-control-plane-7xkrx, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-mhc-remediation-1097yo-control-plane-7xkrx, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-mhc-remediation-1097yo-control-plane-7xkrx, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-gq65w, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-mhc-remediation-1097yo-control-plane-7xkrx, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-6fxvq, container calico-node: http2: client connection lost
STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
INFO: Deleting namespace mhc-remediation-zggem2
STEP: Redacting sensitive information from logs


• [SLOW TEST:1085.920 seconds]
... skipping 70 lines ...
Sep  4 21:14:53.364: INFO: Collecting boot logs for AzureMachine md-rollout-2r2g36-md-0-c4a3d5-7xb4w

Sep  4 21:14:53.679: INFO: Collecting logs for Windows node md-rollou-vbcvx in cluster md-rollout-2r2g36 in namespace md-rollout-lnmqeh

Sep  4 21:16:22.539: INFO: Collecting boot logs for AzureMachine md-rollout-2r2g36-md-win-fom44g-vbcvx

Failed to get logs for machine md-rollout-2r2g36-md-win-5fb4c6d555-f4hl6, cluster md-rollout-lnmqeh/md-rollout-2r2g36: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Sep  4 21:16:22.891: INFO: Collecting logs for Windows node md-rollou-942kh in cluster md-rollout-2r2g36 in namespace md-rollout-lnmqeh

Sep  4 21:17:49.655: INFO: Collecting boot logs for AzureMachine md-rollout-2r2g36-md-win-942kh

Failed to get logs for machine md-rollout-2r2g36-md-win-f7b9744b9-7zgnh, cluster md-rollout-lnmqeh/md-rollout-2r2g36: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Failed to get logs for machine md-rollout-2r2g36-md-win-f7b9744b9-p8k4b, cluster md-rollout-lnmqeh/md-rollout-2r2g36: azuremachines.infrastructure.cluster.x-k8s.io "md-rollout-2r2g36-md-win-lv77k" not found
STEP: Dumping workload cluster md-rollout-lnmqeh/md-rollout-2r2g36 kube-system pod logs
STEP: Collecting events for Pod kube-system/calico-node-vs6js
STEP: Fetching kube-system pod logs took 679.981104ms
STEP: Dumping workload cluster md-rollout-lnmqeh/md-rollout-2r2g36 Azure activity log
STEP: Creating log watcher for controller kube-system/calico-node-tbtrc, container calico-node
STEP: Collecting events for Pod kube-system/calico-node-tbtrc
... skipping 6 lines ...
STEP: Collecting events for Pod kube-system/csi-proxy-jd5hf
STEP: Creating log watcher for controller kube-system/etcd-md-rollout-2r2g36-control-plane-jwj57, container etcd
STEP: Creating log watcher for controller kube-system/csi-proxy-fjgv2, container csi-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-85cqp, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-apiserver-md-rollout-2r2g36-control-plane-jwj57
STEP: Collecting events for Pod kube-system/etcd-md-rollout-2r2g36-control-plane-jwj57
STEP: failed to find events of Pod "etcd-md-rollout-2r2g36-control-plane-jwj57"
STEP: Collecting events for Pod kube-system/kube-controller-manager-md-rollout-2r2g36-control-plane-jwj57
STEP: Creating log watcher for controller kube-system/kube-controller-manager-md-rollout-2r2g36-control-plane-jwj57, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-tsgnz, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-windows-85cqp
STEP: Creating log watcher for controller kube-system/containerd-logger-wmv6b, container containerd-logger
STEP: Collecting events for Pod kube-system/calico-node-windows-wwrfn
... skipping 13 lines ...
STEP: Creating log watcher for controller kube-system/kube-proxy-xzvcz, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-xzvcz
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-4j89l, container coredns
STEP: Collecting events for Pod kube-system/kube-scheduler-md-rollout-2r2g36-control-plane-jwj57
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-8pmn9
STEP: Creating log watcher for controller kube-system/kube-apiserver-md-rollout-2r2g36-control-plane-jwj57, container kube-apiserver
STEP: failed to find events of Pod "kube-apiserver-md-rollout-2r2g36-control-plane-jwj57"
STEP: failed to find events of Pod "kube-controller-manager-md-rollout-2r2g36-control-plane-jwj57"
STEP: failed to find events of Pod "kube-scheduler-md-rollout-2r2g36-control-plane-jwj57"
STEP: Fetching activity logs took 3.591472586s
STEP: Dumping all the Cluster API resources in the "md-rollout-lnmqeh" namespace
STEP: Deleting cluster md-rollout-lnmqeh/md-rollout-2r2g36
STEP: Deleting cluster md-rollout-2r2g36
INFO: Waiting for the Cluster md-rollout-lnmqeh/md-rollout-2r2g36 to be deleted
STEP: Waiting for cluster md-rollout-2r2g36 to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-85cqp, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-nhqc9, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-md-rollout-2r2g36-control-plane-jwj57, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-tsgnz, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-z59wk, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-4j89l, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-z59wk, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-md-rollout-2r2g36-control-plane-jwj57, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-wmv6b, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-njh8t, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-fjgv2, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-md-rollout-2r2g36-control-plane-jwj57, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-md-rollout-2r2g36-control-plane-jwj57, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-wwrfn, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-xzvcz, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-hv5k4, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-wwrfn, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-vs6js, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-8pmn9, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-tbtrc, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-jd5hf, container csi-proxy: http2: client connection lost
STEP: Deleting namespace used for hosting the "md-rollout" test spec
INFO: Deleting namespace md-rollout-lnmqeh
STEP: Redacting sensitive information from logs


• [SLOW TEST:2791.126 seconds]
... skipping 119 lines ...
STEP: Fetching activity logs took 2.384675354s
STEP: Dumping all the Cluster API resources in the "mhc-remediation-99xst6" namespace
STEP: Deleting cluster mhc-remediation-99xst6/mhc-remediation-am6xr9
STEP: Deleting cluster mhc-remediation-am6xr9
INFO: Waiting for the Cluster mhc-remediation-99xst6/mhc-remediation-am6xr9 to be deleted
STEP: Waiting for cluster mhc-remediation-am6xr9 to be deleted
STEP: Got error while streaming logs for pod kube-system/calico-node-h8spj, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-mhc-remediation-am6xr9-control-plane-z4sbm, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-mhc-remediation-am6xr9-control-plane-22mqs, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-mhc-remediation-am6xr9-control-plane-wqstn, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-49xd8, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-mhc-remediation-am6xr9-control-plane-22mqs, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-66847, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-bpx82, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-cdvlf, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-98wnk, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-mhc-remediation-am6xr9-control-plane-z4sbm, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-mhc-remediation-am6xr9-control-plane-wqstn, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-mhc-remediation-am6xr9-control-plane-z4sbm, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-mhc-remediation-am6xr9-control-plane-z4sbm, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-cdr4m, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-mhc-remediation-am6xr9-control-plane-22mqs, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-mhc-remediation-am6xr9-control-plane-wqstn, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-mhc-remediation-am6xr9-control-plane-22mqs, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-ddppz, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-rpjnr, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-mhc-remediation-am6xr9-control-plane-wqstn, container kube-apiserver: http2: client connection lost
STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
INFO: Deleting namespace mhc-remediation-99xst6
STEP: Redacting sensitive information from logs


• [SLOW TEST:1110.493 seconds]
... skipping 48 lines ...
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-jc4k4
STEP: Collecting events for Pod kube-system/kube-controller-manager-kcp-adoption-hhtua0-control-plane-0
STEP: Creating log watcher for controller kube-system/etcd-kcp-adoption-hhtua0-control-plane-0, container etcd
STEP: Collecting events for Pod kube-system/calico-node-xlbft
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-jc4k4, container coredns
STEP: Collecting events for Pod kube-system/kube-proxy-9btmx
STEP: failed to find events of Pod "kube-controller-manager-kcp-adoption-hhtua0-control-plane-0"
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-wplpv
STEP: Creating log watcher for controller kube-system/kube-scheduler-kcp-adoption-hhtua0-control-plane-0, container kube-scheduler
STEP: Dumping workload cluster kcp-adoption-m5es46/kcp-adoption-hhtua0 Azure activity log
STEP: Creating log watcher for controller kube-system/kube-proxy-9btmx, container kube-proxy
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-kgpfc
STEP: Collecting events for Pod kube-system/etcd-kcp-adoption-hhtua0-control-plane-0
STEP: failed to find events of Pod "etcd-kcp-adoption-hhtua0-control-plane-0"
STEP: Creating log watcher for controller kube-system/kube-apiserver-kcp-adoption-hhtua0-control-plane-0, container kube-apiserver
STEP: Collecting events for Pod kube-system/kube-scheduler-kcp-adoption-hhtua0-control-plane-0
STEP: Collecting events for Pod kube-system/kube-apiserver-kcp-adoption-hhtua0-control-plane-0
STEP: failed to find events of Pod "kube-scheduler-kcp-adoption-hhtua0-control-plane-0"
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-wplpv, container coredns
STEP: failed to find events of Pod "kube-apiserver-kcp-adoption-hhtua0-control-plane-0"
STEP: Creating log watcher for controller kube-system/kube-controller-manager-kcp-adoption-hhtua0-control-plane-0, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/calico-node-xlbft, container calico-node
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-kgpfc, container calico-kube-controllers
STEP: Fetching activity logs took 2.246742537s
STEP: Dumping all the Cluster API resources in the "kcp-adoption-m5es46" namespace
STEP: Deleting cluster kcp-adoption-m5es46/kcp-adoption-hhtua0
... skipping 94 lines ...
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-ms745
STEP: Collecting events for Pod kube-system/calico-node-q7nrf
STEP: Creating log watcher for controller kube-system/calico-node-q7nrf, container calico-node
STEP: Fetching kube-system pod logs took 712.972589ms
STEP: Dumping workload cluster machine-pool-q946in/machine-pool-ri6cap Azure activity log
STEP: Collecting events for Pod kube-system/kube-scheduler-machine-pool-ri6cap-control-plane-2gcph
STEP: failed to find events of Pod "kube-scheduler-machine-pool-ri6cap-control-plane-2gcph"
STEP: Collecting events for Pod kube-system/calico-node-st6x7
STEP: Creating log watcher for controller kube-system/calico-node-windows-v6v2q, container calico-node-startup
STEP: Creating log watcher for controller kube-system/calico-node-windows-v6v2q, container calico-node-felix
STEP: Collecting events for Pod kube-system/calico-node-windows-v6v2q
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-dmkqg, container coredns
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-dmkqg
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-ndxt4, container coredns
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-ndxt4
STEP: Creating log watcher for controller kube-system/etcd-machine-pool-ri6cap-control-plane-2gcph, container etcd
STEP: Collecting events for Pod kube-system/etcd-machine-pool-ri6cap-control-plane-2gcph
STEP: Creating log watcher for controller kube-system/kube-apiserver-machine-pool-ri6cap-control-plane-2gcph, container kube-apiserver
STEP: failed to find events of Pod "etcd-machine-pool-ri6cap-control-plane-2gcph"
STEP: Collecting events for Pod kube-system/kube-apiserver-machine-pool-ri6cap-control-plane-2gcph
STEP: Creating log watcher for controller kube-system/kube-controller-manager-machine-pool-ri6cap-control-plane-2gcph, container kube-controller-manager
STEP: failed to find events of Pod "kube-apiserver-machine-pool-ri6cap-control-plane-2gcph"
STEP: Collecting events for Pod kube-system/kube-controller-manager-machine-pool-ri6cap-control-plane-2gcph
STEP: failed to find events of Pod "kube-controller-manager-machine-pool-ri6cap-control-plane-2gcph"
STEP: Error starting logs stream for pod kube-system/kube-proxy-windows-8s8ks, container kube-proxy: pods "win-p-win000002" not found
STEP: Error starting logs stream for pod kube-system/calico-node-windows-v6v2q, container calico-node-felix: pods "win-p-win000002" not found
STEP: Error starting logs stream for pod kube-system/calico-node-windows-v6v2q, container calico-node-startup: pods "win-p-win000002" not found
STEP: Fetching activity logs took 1.723946696s
STEP: Dumping all the Cluster API resources in the "machine-pool-q946in" namespace
STEP: Deleting cluster machine-pool-q946in/machine-pool-ri6cap
STEP: Deleting cluster machine-pool-ri6cap
INFO: Waiting for the Cluster machine-pool-q946in/machine-pool-ri6cap to be deleted
STEP: Waiting for cluster machine-pool-ri6cap to be deleted
STEP: Error starting logs stream for pod kube-system/calico-node-st6x7, container calico-node: Get "https://10.1.0.4:10250/containerLogs/kube-system/calico-node-st6x7/calico-node?follow=true": dial tcp 10.1.0.4:10250: i/o timeout
STEP: Error starting logs stream for pod kube-system/kube-proxy-z8z6g, container kube-proxy: Get "https://10.1.0.8:10250/containerLogs/kube-system/kube-proxy-z8z6g/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-lkkkf, container kube-proxy: Get "https://10.1.0.4:10250/containerLogs/kube-system/kube-proxy-lkkkf/kube-proxy?follow=true": dial tcp 10.1.0.4:10250: i/o timeout
STEP: Error starting logs stream for pod kube-system/kube-proxy-55b5l, container kube-proxy: Get "https://10.1.0.5:10250/containerLogs/kube-system/kube-proxy-55b5l/kube-proxy?follow=true": dial tcp 10.1.0.5:10250: i/o timeout
STEP: Error starting logs stream for pod kube-system/calico-node-k65fh, container calico-node: Get "https://10.1.0.8:10250/containerLogs/kube-system/calico-node-k65fh/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-q7nrf, container calico-node: Get "https://10.1.0.5:10250/containerLogs/kube-system/calico-node-q7nrf/calico-node?follow=true": dial tcp 10.1.0.5:10250: i/o timeout
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-machine-pool-ri6cap-control-plane-2gcph, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-ndxt4, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-hlctb, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-machine-pool-ri6cap-control-plane-2gcph, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-machine-pool-ri6cap-control-plane-2gcph, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-dmkqg, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-machine-pool-ri6cap-control-plane-2gcph, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-6jqxz, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-ms745, container calico-kube-controllers: http2: client connection lost
STEP: Deleting namespace used for hosting the "machine-pool" test spec
INFO: Deleting namespace machine-pool-q946in
STEP: Redacting sensitive information from logs


• [SLOW TEST:1243.437 seconds]
... skipping 67 lines ...
Sep  4 21:44:44.042: INFO: Collecting boot logs for AzureMachine md-scale-cabnil-md-0-nch8g

Sep  4 21:44:44.615: INFO: Collecting logs for Windows node md-scale-gv46s in cluster md-scale-cabnil in namespace md-scale-n59rna

Sep  4 21:46:12.119: INFO: Collecting boot logs for AzureMachine md-scale-cabnil-md-win-gv46s

Failed to get logs for machine md-scale-cabnil-md-win-cb946cb55-67m77, cluster md-scale-n59rna/md-scale-cabnil: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Sep  4 21:46:12.603: INFO: Collecting logs for Windows node md-scale-f6bjc in cluster md-scale-cabnil in namespace md-scale-n59rna

Sep  4 21:47:40.053: INFO: Collecting boot logs for AzureMachine md-scale-cabnil-md-win-f6bjc

Failed to get logs for machine md-scale-cabnil-md-win-cb946cb55-r49r8, cluster md-scale-n59rna/md-scale-cabnil: running command "Get-Content "C:\\cni.log"": Process exited with status 1
STEP: Dumping workload cluster md-scale-n59rna/md-scale-cabnil kube-system pod logs
STEP: Collecting events for Pod kube-system/calico-node-qckwz
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-tm5hc
STEP: Collecting events for Pod kube-system/containerd-logger-5bmqj
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-jjbhg
STEP: Collecting events for Pod kube-system/kube-controller-manager-md-scale-cabnil-control-plane-4gkkx
STEP: Fetching kube-system pod logs took 676.426251ms
STEP: Dumping workload cluster md-scale-n59rna/md-scale-cabnil Azure activity log
STEP: failed to find events of Pod "kube-controller-manager-md-scale-cabnil-control-plane-4gkkx"
STEP: Creating log watcher for controller kube-system/csi-proxy-h4b5g, container csi-proxy
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-jjbhg, container calico-kube-controllers
STEP: Creating log watcher for controller kube-system/containerd-logger-q8kjp, container containerd-logger
STEP: Creating log watcher for controller kube-system/calico-node-windows-6q9ff, container calico-node-felix
STEP: Collecting events for Pod kube-system/kube-scheduler-md-scale-cabnil-control-plane-4gkkx
STEP: Collecting events for Pod kube-system/csi-proxy-h4b5g
STEP: Creating log watcher for controller kube-system/calico-node-qckwz, container calico-node
STEP: failed to find events of Pod "kube-scheduler-md-scale-cabnil-control-plane-4gkkx"
STEP: Collecting events for Pod kube-system/calico-node-windows-6q9ff
STEP: Collecting events for Pod kube-system/calico-node-dl5vd
STEP: Creating log watcher for controller kube-system/calico-node-windows-j68q5, container calico-node-startup
STEP: Creating log watcher for controller kube-system/calico-node-windows-j68q5, container calico-node-felix
STEP: Collecting events for Pod kube-system/containerd-logger-q8kjp
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-2bfg4, container coredns
... skipping 10 lines ...
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-mhl2n, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-dswl7
STEP: Creating log watcher for controller kube-system/kube-scheduler-md-scale-cabnil-control-plane-4gkkx, container kube-scheduler
STEP: Creating log watcher for controller kube-system/etcd-md-scale-cabnil-control-plane-4gkkx, container etcd
STEP: Collecting events for Pod kube-system/kube-proxy-windows-bxkrh
STEP: Collecting events for Pod kube-system/etcd-md-scale-cabnil-control-plane-4gkkx
STEP: failed to find events of Pod "etcd-md-scale-cabnil-control-plane-4gkkx"
STEP: Creating log watcher for controller kube-system/kube-proxy-lvzvk, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-controller-manager-md-scale-cabnil-control-plane-4gkkx, container kube-controller-manager
STEP: Collecting events for Pod kube-system/csi-proxy-pnvhl
STEP: Collecting events for Pod kube-system/kube-apiserver-md-scale-cabnil-control-plane-4gkkx
STEP: failed to find events of Pod "kube-apiserver-md-scale-cabnil-control-plane-4gkkx"
STEP: Creating log watcher for controller kube-system/calico-node-windows-6q9ff, container calico-node-startup
STEP: Creating log watcher for controller kube-system/calico-node-dl5vd, container calico-node
STEP: Fetching activity logs took 3.675195723s
STEP: Dumping all the Cluster API resources in the "md-scale-n59rna" namespace
STEP: Deleting cluster md-scale-n59rna/md-scale-cabnil
STEP: Deleting cluster md-scale-cabnil
INFO: Waiting for the Cluster md-scale-n59rna/md-scale-cabnil to be deleted
STEP: Waiting for cluster md-scale-cabnil to be deleted
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-6q9ff, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-mhl2n, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-md-scale-cabnil-control-plane-4gkkx, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-dswl7, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-h4b5g, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-md-scale-cabnil-control-plane-4gkkx, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-md-scale-cabnil-control-plane-4gkkx, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-pnvhl, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-6q9ff, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-bxkrh, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-q8kjp, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-2bfg4, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-j68q5, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-5bmqj, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-qckwz, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-jjbhg, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-j68q5, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-tm5hc, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-md-scale-cabnil-control-plane-4gkkx, container kube-scheduler: http2: client connection lost
STEP: Deleting namespace used for hosting the "md-scale" test spec
INFO: Deleting namespace md-scale-n59rna
STEP: Redacting sensitive information from logs


• [SLOW TEST:1692.338 seconds]
... skipping 56 lines ...
STEP: Dumping logs from the "node-drain-kn70mu" workload cluster
STEP: Dumping workload cluster node-drain-4muxlr/node-drain-kn70mu logs
Sep  4 21:47:53.736: INFO: Collecting logs for Linux node node-drain-kn70mu-control-plane-7km2f in cluster node-drain-kn70mu in namespace node-drain-4muxlr

Sep  4 21:54:27.681: INFO: Collecting boot logs for AzureMachine node-drain-kn70mu-control-plane-7km2f

Failed to get logs for machine node-drain-kn70mu-control-plane-mnwmr, cluster node-drain-4muxlr/node-drain-kn70mu: dialing public load balancer at node-drain-kn70mu-ad76bbc5.westus3.cloudapp.azure.com: dial tcp 20.171.209.60:22: connect: connection timed out
STEP: Dumping workload cluster node-drain-4muxlr/node-drain-kn70mu kube-system pod logs
STEP: Fetching kube-system pod logs took 688.499351ms
STEP: Creating log watcher for controller kube-system/calico-node-b87rq, container calico-node
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-p6llc, container coredns
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-vnjln, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/kube-apiserver-node-drain-kn70mu-control-plane-7km2f
... skipping 32 lines ...
    /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.4/e2e/node_drain_timeout.go:82
------------------------------
STEP: Tearing down the management cluster


Ran 9 of 23 Specs in 5072.725 seconds
SUCCESS! -- 9 Passed | 0 Failed | 0 Pending | 14 Skipped


Ginkgo ran 1 suite in 1h26m18.539633356s
Test Suite Passed
make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
================ REDACTING LOGS ================
... skipping 10 lines ...