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

No Test Failures!


Show 9 Passed Tests

Show 14 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-kind2620189713
INFO: Loading image: "capzci.azurecr.io/cluster-api-azure-controller-amd64:20220907203013"
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-tar665504740/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-tar3380434622/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-tar1267187807/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-wxb2d, 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  7 20:39:57.885: INFO: starting to create namespace for hosting the "self-hosted" test spec
2022/09/07 20:39:57 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-sk3vd4" 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-sk3vd4 --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/coredns-78fcd69978-fj98v
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-hjgqx, container coredns
STEP: Creating log watcher for controller kube-system/kube-apiserver-self-hosted-sk3vd4-control-plane-h4mnw, container kube-apiserver
STEP: Collecting events for Pod kube-system/kube-apiserver-self-hosted-sk3vd4-control-plane-h4mnw
STEP: Creating log watcher for controller kube-system/kube-controller-manager-self-hosted-sk3vd4-control-plane-h4mnw, container kube-controller-manager
STEP: Dumping workload cluster self-hosted/self-hosted-sk3vd4 Azure activity log
STEP: failed to find events of Pod "kube-apiserver-self-hosted-sk3vd4-control-plane-h4mnw"
STEP: Collecting events for Pod kube-system/etcd-self-hosted-sk3vd4-control-plane-h4mnw
STEP: failed to find events of Pod "etcd-self-hosted-sk3vd4-control-plane-h4mnw"
STEP: Collecting events for Pod kube-system/kube-controller-manager-self-hosted-sk3vd4-control-plane-h4mnw
STEP: Creating log watcher for controller kube-system/etcd-self-hosted-sk3vd4-control-plane-h4mnw, container etcd
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-l6gnt
STEP: Creating log watcher for controller kube-system/calico-node-2xwvp, container calico-node
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-l6gnt, container calico-kube-controllers
STEP: Creating log watcher for controller kube-system/kube-proxy-pz4m9, container kube-proxy
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-hjgqx
STEP: Collecting events for Pod kube-system/kube-proxy-pz4m9
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-fj98v, container coredns
STEP: failed to find events of Pod "kube-controller-manager-self-hosted-sk3vd4-control-plane-h4mnw"
STEP: Creating log watcher for controller kube-system/kube-proxy-rj78w, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-rj78w
STEP: Creating log watcher for controller kube-system/calico-node-brjsf, container calico-node
STEP: Creating log watcher for controller kube-system/kube-scheduler-self-hosted-sk3vd4-control-plane-h4mnw, container kube-scheduler
STEP: Collecting events for Pod kube-system/kube-scheduler-self-hosted-sk3vd4-control-plane-h4mnw
STEP: failed to find events of Pod "kube-scheduler-self-hosted-sk3vd4-control-plane-h4mnw"
STEP: Fetching activity logs took 1.559954898s
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-sk3vd4
INFO: Waiting for the Cluster self-hosted/self-hosted-sk3vd4 to be deleted
STEP: Waiting for cluster self-hosted-sk3vd4 to be deleted
... skipping 67 lines ...
Sep  7 20:49:33.410: INFO: Collecting boot logs for AzureMachine quick-start-rm55ks-md-0-26cmm

Sep  7 20:49:33.735: INFO: Collecting logs for Windows node quick-sta-zrkq9 in cluster quick-start-rm55ks in namespace quick-start-xwa1je

Sep  7 20:50:57.174: INFO: Collecting boot logs for AzureMachine quick-start-rm55ks-md-win-zrkq9

Failed to get logs for machine quick-start-rm55ks-md-win-5b479f5fc9-rfv6d, cluster quick-start-xwa1je/quick-start-rm55ks: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Sep  7 20:50:57.453: INFO: Collecting logs for Windows node quick-sta-dq464 in cluster quick-start-rm55ks in namespace quick-start-xwa1je

Sep  7 20:52:19.371: INFO: Collecting boot logs for AzureMachine quick-start-rm55ks-md-win-dq464

Failed to get logs for machine quick-start-rm55ks-md-win-5b479f5fc9-rhjr8, cluster quick-start-xwa1je/quick-start-rm55ks: running command "Get-Content "C:\\cni.log"": Process exited with status 1
STEP: Dumping workload cluster quick-start-xwa1je/quick-start-rm55ks kube-system pod logs
STEP: Creating log watcher for controller kube-system/calico-node-windows-vmhjx, container calico-node-felix
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-f2lnz
STEP: Creating log watcher for controller kube-system/calico-node-n74ct, container calico-node
STEP: Creating log watcher for controller kube-system/calico-node-windows-9lwm4, container calico-node-felix
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-f2lnz, container calico-kube-controllers
... skipping 31 lines ...
STEP: Creating log watcher for controller kube-system/kube-scheduler-quick-start-rm55ks-control-plane-c7rsr, container kube-scheduler
STEP: Creating log watcher for controller kube-system/kube-proxy-n7xrk, container kube-proxy
STEP: Creating log watcher for controller kube-system/etcd-quick-start-rm55ks-control-plane-c7rsr, container etcd
STEP: Collecting events for Pod kube-system/kube-proxy-c9zws
STEP: Collecting events for Pod kube-system/kube-proxy-n7xrk
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-wpc97, container kube-proxy
STEP: failed to find events of Pod "kube-scheduler-quick-start-rm55ks-control-plane-c7rsr"
STEP: failed to find events of Pod "kube-controller-manager-quick-start-rm55ks-control-plane-c7rsr"
STEP: failed to find events of Pod "etcd-quick-start-rm55ks-control-plane-c7rsr"
STEP: failed to find events of Pod "kube-apiserver-quick-start-rm55ks-control-plane-c7rsr"
STEP: Fetching activity logs took 1.289302141s
STEP: Dumping all the Cluster API resources in the "quick-start-xwa1je" namespace
STEP: Deleting cluster quick-start-xwa1je/quick-start-rm55ks
STEP: Deleting cluster quick-start-rm55ks
INFO: Waiting for the Cluster quick-start-xwa1je/quick-start-rm55ks to be deleted
STEP: Waiting for cluster quick-start-rm55ks to be deleted
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-9lwm4, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-quick-start-rm55ks-control-plane-c7rsr, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-c9zws, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-quick-start-rm55ks-control-plane-c7rsr, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-wpc97, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-d67zm, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-659nt, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-tg5gd, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-quick-start-rm55ks-control-plane-c7rsr, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-9lwm4, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-vbfq4, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-9psk4, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-quick-start-rm55ks-control-plane-c7rsr, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-f2lnz, container calico-kube-controllers: http2: client connection lost
STEP: Deleting namespace used for hosting the "quick-start" test spec
INFO: Deleting namespace quick-start-xwa1je
STEP: Redacting sensitive information from logs


• [SLOW TEST:1067.504 seconds]
... skipping 70 lines ...
Sep  7 20:57:06.761: INFO: Collecting boot logs for AzureMachine md-rollout-oct91o-md-0-7r4en0-99jdp

Sep  7 20:57:07.111: INFO: Collecting logs for Windows node md-rollou-6dshs in cluster md-rollout-oct91o in namespace md-rollout-tt5gj6

Sep  7 20:58:35.524: INFO: Collecting boot logs for AzureMachine md-rollout-oct91o-md-win-man18d-6dshs

Failed to get logs for machine md-rollout-oct91o-md-win-5547674556-x9zzj, cluster md-rollout-tt5gj6/md-rollout-oct91o: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Failed to get logs for machine md-rollout-oct91o-md-win-7d445c554d-4njxc, cluster md-rollout-tt5gj6/md-rollout-oct91o: azuremachines.infrastructure.cluster.x-k8s.io "md-rollout-oct91o-md-win-942lf" not found
Sep  7 20:58:36.100: INFO: Collecting logs for Windows node md-rollou-nvfrz in cluster md-rollout-oct91o in namespace md-rollout-tt5gj6

Sep  7 21:00:05.100: INFO: Collecting boot logs for AzureMachine md-rollout-oct91o-md-win-nvfrz

Failed to get logs for machine md-rollout-oct91o-md-win-7d445c554d-8wdjh, cluster md-rollout-tt5gj6/md-rollout-oct91o: running command "Get-Content "C:\\cni.log"": Process exited with status 1
STEP: Dumping workload cluster md-rollout-tt5gj6/md-rollout-oct91o kube-system pod logs
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-n7g74
STEP: Collecting events for Pod kube-system/kube-scheduler-md-rollout-oct91o-control-plane-k8l4c
STEP: Creating log watcher for controller kube-system/csi-proxy-g6vp9, container csi-proxy
STEP: Collecting events for Pod kube-system/kube-controller-manager-md-rollout-oct91o-control-plane-k8l4c
STEP: Fetching kube-system pod logs took 519.675178ms
STEP: Dumping workload cluster md-rollout-tt5gj6/md-rollout-oct91o Azure activity log
STEP: failed to find events of Pod "kube-controller-manager-md-rollout-oct91o-control-plane-k8l4c"
STEP: Collecting events for Pod kube-system/csi-proxy-g6vp9
STEP: Collecting events for Pod kube-system/etcd-md-rollout-oct91o-control-plane-k8l4c
STEP: Creating log watcher for controller kube-system/calico-node-windows-xwm66, container calico-node-felix
STEP: failed to find events of Pod "kube-scheduler-md-rollout-oct91o-control-plane-k8l4c"
STEP: Creating log watcher for controller kube-system/calico-node-2n4t6, container calico-node
STEP: Creating log watcher for controller kube-system/kube-proxy-mk4zk, container kube-proxy
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-n7g74, container calico-kube-controllers
STEP: Creating log watcher for controller kube-system/kube-apiserver-md-rollout-oct91o-control-plane-k8l4c, container kube-apiserver
STEP: Collecting events for Pod kube-system/calico-node-2n4t6
STEP: failed to find events of Pod "etcd-md-rollout-oct91o-control-plane-k8l4c"
STEP: Creating log watcher for controller kube-system/csi-proxy-gk6vv, container csi-proxy
STEP: Creating log watcher for controller kube-system/calico-node-windows-pbxm7, container calico-node-felix
STEP: Collecting events for Pod kube-system/csi-proxy-gk6vv
STEP: Creating log watcher for controller kube-system/etcd-md-rollout-oct91o-control-plane-k8l4c, container etcd
STEP: Creating log watcher for controller kube-system/calico-node-windows-pbxm7, container calico-node-startup
STEP: Creating log watcher for controller kube-system/calico-node-grdhx, container calico-node
... skipping 2 lines ...
STEP: Collecting events for Pod kube-system/calico-node-windows-xwm66
STEP: Creating log watcher for controller kube-system/containerd-logger-6rb4v, container containerd-logger
STEP: Collecting events for Pod kube-system/calico-node-grdhx
STEP: Collecting events for Pod kube-system/containerd-logger-6rb4v
STEP: Collecting events for Pod kube-system/kube-apiserver-md-rollout-oct91o-control-plane-k8l4c
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-qw4pq
STEP: failed to find events of Pod "kube-apiserver-md-rollout-oct91o-control-plane-k8l4c"
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-xxcdz, container coredns
STEP: Creating log watcher for controller kube-system/calico-node-windows-xwm66, container calico-node-startup
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-8l7kx, container kube-proxy
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-xxcdz
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-nq29g, container kube-proxy
STEP: Creating log watcher for controller kube-system/containerd-logger-8n8hd, container containerd-logger
... skipping 8 lines ...
STEP: Fetching activity logs took 2.028117498s
STEP: Dumping all the Cluster API resources in the "md-rollout-tt5gj6" namespace
STEP: Deleting cluster md-rollout-tt5gj6/md-rollout-oct91o
STEP: Deleting cluster md-rollout-oct91o
INFO: Waiting for the Cluster md-rollout-tt5gj6/md-rollout-oct91o to be deleted
STEP: Waiting for cluster md-rollout-oct91o to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-8l7kx, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-pbxm7, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-xwm66, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-ts2fk, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-md-rollout-oct91o-control-plane-k8l4c, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-n7g74, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-qw4pq, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-6rb4v, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-md-rollout-oct91o-control-plane-k8l4c, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-md-rollout-oct91o-control-plane-k8l4c, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-grdhx, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-g6vp9, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-gk6vv, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-md-rollout-oct91o-control-plane-k8l4c, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-pbxm7, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-2n4t6, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-xxcdz, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-mk4zk, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-xwm66, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-nq29g, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-8n8hd, container containerd-logger: http2: client connection lost
STEP: Deleting namespace used for hosting the "md-rollout" test spec
INFO: Deleting namespace md-rollout-tt5gj6
STEP: Redacting sensitive information from logs


• [SLOW TEST:1648.148 seconds]
... skipping 85 lines ...
STEP: Fetching activity logs took 1.371775953s
STEP: Dumping all the Cluster API resources in the "mhc-remediation-oz3wp0" namespace
STEP: Deleting cluster mhc-remediation-oz3wp0/mhc-remediation-hz5et2
STEP: Deleting cluster mhc-remediation-hz5et2
INFO: Waiting for the Cluster mhc-remediation-oz3wp0/mhc-remediation-hz5et2 to be deleted
STEP: Waiting for cluster mhc-remediation-hz5et2 to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-proxy-ctzbg, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-k8ww4, container calico-node: http2: client connection lost
STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
INFO: Deleting namespace mhc-remediation-oz3wp0
STEP: Redacting sensitive information from logs


• [SLOW TEST:961.353 seconds]
... skipping 119 lines ...
STEP: Fetching activity logs took 1.997067545s
STEP: Dumping all the Cluster API resources in the "mhc-remediation-4anlsw" namespace
STEP: Deleting cluster mhc-remediation-4anlsw/mhc-remediation-qz5qbn
STEP: Deleting cluster mhc-remediation-qz5qbn
INFO: Waiting for the Cluster mhc-remediation-4anlsw/mhc-remediation-qz5qbn to be deleted
STEP: Waiting for cluster mhc-remediation-qz5qbn to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-proxy-bzvd6, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-mhc-remediation-qz5qbn-control-plane-9fndz, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-mhc-remediation-qz5qbn-control-plane-7j7wn, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-hbpl6, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-pjd2c, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-6x94c, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-sbfdw, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-mhc-remediation-qz5qbn-control-plane-9fndz, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-tppg8, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-kljrt, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-mhc-remediation-qz5qbn-control-plane-7j7wn, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-mhc-remediation-qz5qbn-control-plane-9fndz, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-mhc-remediation-qz5qbn-control-plane-9fndz, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-mhc-remediation-qz5qbn-control-plane-7j7wn, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-mhc-remediation-qz5qbn-control-plane-7j7wn, container kube-controller-manager: http2: client connection lost
STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
INFO: Deleting namespace mhc-remediation-4anlsw
STEP: Redacting sensitive information from logs


• [SLOW TEST:1155.069 seconds]
... skipping 52 lines ...
STEP: Fetching kube-system pod logs took 271.702458ms
STEP: Dumping workload cluster kcp-adoption-sld157/kcp-adoption-x393e8 Azure activity log
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-mwsw4, container coredns
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-n8bdz
STEP: Collecting events for Pod kube-system/kube-apiserver-kcp-adoption-x393e8-control-plane-0
STEP: Creating log watcher for controller kube-system/etcd-kcp-adoption-x393e8-control-plane-0, container etcd
STEP: failed to find events of Pod "kube-apiserver-kcp-adoption-x393e8-control-plane-0"
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-gfwds
STEP: Creating log watcher for controller kube-system/calico-node-wswmf, container calico-node
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-mwsw4
STEP: Collecting events for Pod kube-system/kube-scheduler-kcp-adoption-x393e8-control-plane-0
STEP: failed to find events of Pod "kube-scheduler-kcp-adoption-x393e8-control-plane-0"
STEP: Collecting events for Pod kube-system/etcd-kcp-adoption-x393e8-control-plane-0
STEP: Collecting events for Pod kube-system/kube-controller-manager-kcp-adoption-x393e8-control-plane-0
STEP: failed to find events of Pod "etcd-kcp-adoption-x393e8-control-plane-0"
STEP: Creating log watcher for controller kube-system/kube-proxy-vbdbq, container kube-proxy
STEP: failed to find events of Pod "kube-controller-manager-kcp-adoption-x393e8-control-plane-0"
STEP: Collecting events for Pod kube-system/kube-proxy-vbdbq
STEP: Creating log watcher for controller kube-system/kube-controller-manager-kcp-adoption-x393e8-control-plane-0, container kube-controller-manager
STEP: Fetching activity logs took 1.177580959s
STEP: Dumping all the Cluster API resources in the "kcp-adoption-sld157" namespace
STEP: Deleting cluster kcp-adoption-sld157/kcp-adoption-x393e8
STEP: Deleting cluster kcp-adoption-x393e8
INFO: Waiting for the Cluster kcp-adoption-sld157/kcp-adoption-x393e8 to be deleted
STEP: Waiting for cluster kcp-adoption-x393e8 to be deleted
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-gfwds, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-kcp-adoption-x393e8-control-plane-0, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-kcp-adoption-x393e8-control-plane-0, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-kcp-adoption-x393e8-control-plane-0, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-mwsw4, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-wswmf, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-n8bdz, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-vbdbq, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-kcp-adoption-x393e8-control-plane-0, container kube-controller-manager: http2: client connection lost
STEP: Deleting namespace used for hosting the "kcp-adoption" test spec
INFO: Deleting namespace kcp-adoption-sld157
STEP: Redacting sensitive information from logs


• [SLOW TEST:588.876 seconds]
... skipping 99 lines ...
STEP: Fetching kube-system pod logs took 477.805571ms
STEP: Dumping workload cluster machine-pool-mc4rv3/machine-pool-htxw8x Azure activity log
STEP: Collecting events for Pod kube-system/kube-scheduler-machine-pool-htxw8x-control-plane-z8pjd
STEP: Collecting events for Pod kube-system/kube-proxy-windows-q9s7n
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-q9s7n, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-scheduler-machine-pool-htxw8x-control-plane-z8pjd, container kube-scheduler
STEP: Error starting logs stream for pod kube-system/kube-proxy-windows-q9s7n, container kube-proxy: pods "win-p-win000002" not found
STEP: Error starting logs stream for pod kube-system/calico-node-windows-5zjs2, container calico-node-felix: pods "win-p-win000002" not found
STEP: Error starting logs stream for pod kube-system/calico-node-windows-5zjs2, container calico-node-startup: pods "win-p-win000002" not found
STEP: Fetching activity logs took 1.891922207s
STEP: Dumping all the Cluster API resources in the "machine-pool-mc4rv3" namespace
STEP: Deleting cluster machine-pool-mc4rv3/machine-pool-htxw8x
STEP: Deleting cluster machine-pool-htxw8x
INFO: Waiting for the Cluster machine-pool-mc4rv3/machine-pool-htxw8x to be deleted
STEP: Waiting for cluster machine-pool-htxw8x to be deleted
STEP: Error starting logs stream for pod kube-system/calico-node-gt24c, container calico-node: Get "https://10.1.0.5:10250/containerLogs/kube-system/calico-node-gt24c/calico-node?follow=true": dial tcp 10.1.0.5:10250: i/o timeout
STEP: Error starting logs stream for pod kube-system/kube-proxy-mp4tk, container kube-proxy: Get "https://10.1.0.5:10250/containerLogs/kube-system/kube-proxy-mp4tk/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-tt4dn, container calico-node: Get "https://10.1.0.4:10250/containerLogs/kube-system/calico-node-tt4dn/calico-node?follow=true": dial tcp 10.1.0.4:10250: i/o timeout
STEP: Error starting logs stream for pod kube-system/calico-node-s5cts, container calico-node: Get "https://10.1.0.8:10250/containerLogs/kube-system/calico-node-s5cts/calico-node?follow=true": dial tcp 10.1.0.8:10250: i/o timeout
STEP: Error starting logs stream for pod kube-system/kube-proxy-9pzvc, container kube-proxy: Get "https://10.1.0.8:10250/containerLogs/kube-system/kube-proxy-9pzvc/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-ktctk, container kube-proxy: Get "https://10.1.0.4:10250/containerLogs/kube-system/kube-proxy-ktctk/kube-proxy?follow=true": dial tcp 10.1.0.4:10250: i/o timeout
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-9b8ft, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-g67bj, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-hls7s, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-c2mjk, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-vtkvm, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-machine-pool-htxw8x-control-plane-z8pjd, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-machine-pool-htxw8x-control-plane-z8pjd, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-machine-pool-htxw8x-control-plane-z8pjd, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-machine-pool-htxw8x-control-plane-z8pjd, container kube-apiserver: http2: client connection lost
STEP: Deleting namespace used for hosting the "machine-pool" test spec
INFO: Deleting namespace machine-pool-mc4rv3
STEP: Redacting sensitive information from logs


• [SLOW TEST:1329.629 seconds]
... skipping 67 lines ...
Sep  7 21:28:50.992: INFO: Collecting boot logs for AzureMachine md-scale-k2uqz6-md-0-g8g5n

Sep  7 21:28:51.416: INFO: Collecting logs for Windows node md-scale-5pf44 in cluster md-scale-k2uqz6 in namespace md-scale-sbz5o4

Sep  7 21:30:15.745: INFO: Collecting boot logs for AzureMachine md-scale-k2uqz6-md-win-5pf44

Failed to get logs for machine md-scale-k2uqz6-md-win-759c8ddc65-4zcnm, cluster md-scale-sbz5o4/md-scale-k2uqz6: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Sep  7 21:30:16.022: INFO: Collecting logs for Windows node md-scale-t24zf in cluster md-scale-k2uqz6 in namespace md-scale-sbz5o4

Sep  7 21:31:45.096: INFO: Collecting boot logs for AzureMachine md-scale-k2uqz6-md-win-t24zf

Failed to get logs for machine md-scale-k2uqz6-md-win-759c8ddc65-hqqv5, cluster md-scale-sbz5o4/md-scale-k2uqz6: running command "Get-Content "C:\\cni.log"": Process exited with status 1
STEP: Dumping workload cluster md-scale-sbz5o4/md-scale-k2uqz6 kube-system pod logs
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-sbfgf, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/containerd-logger-4k5dl
STEP: Creating log watcher for controller kube-system/csi-proxy-2vnr6, container csi-proxy
STEP: Fetching kube-system pod logs took 471.805137ms
STEP: Dumping workload cluster md-scale-sbz5o4/md-scale-k2uqz6 Azure activity log
STEP: Collecting events for Pod kube-system/kube-controller-manager-md-scale-k2uqz6-control-plane-d9q4v
STEP: failed to find events of Pod "kube-controller-manager-md-scale-k2uqz6-control-plane-d9q4v"
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-hwp7z, container kube-proxy
STEP: Creating log watcher for controller kube-system/etcd-md-scale-k2uqz6-control-plane-d9q4v, container etcd
STEP: Collecting events for Pod kube-system/kube-proxy-windows-hwp7z
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-sbfgf
STEP: Creating log watcher for controller kube-system/kube-proxy-z2kz8, container kube-proxy
STEP: Collecting events for Pod kube-system/etcd-md-scale-k2uqz6-control-plane-d9q4v
STEP: Creating log watcher for controller kube-system/calico-node-pmpns, container calico-node
STEP: Creating log watcher for controller kube-system/kube-apiserver-md-scale-k2uqz6-control-plane-d9q4v, container kube-apiserver
STEP: Collecting events for Pod kube-system/kube-proxy-5p9p7
STEP: Creating log watcher for controller kube-system/kube-proxy-5p9p7, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-hcwwc, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-apiserver-md-scale-k2uqz6-control-plane-d9q4v
STEP: Collecting events for Pod kube-system/calico-node-t6g7l
STEP: failed to find events of Pod "kube-apiserver-md-scale-k2uqz6-control-plane-d9q4v"
STEP: Collecting events for Pod kube-system/calico-node-pmpns
STEP: Collecting events for Pod kube-system/kube-proxy-z2kz8
STEP: Creating log watcher for controller kube-system/containerd-logger-f6q5m, container containerd-logger
STEP: Creating log watcher for controller kube-system/calico-node-windows-884s7, container calico-node-felix
STEP: Creating log watcher for controller kube-system/kube-scheduler-md-scale-k2uqz6-control-plane-d9q4v, container kube-scheduler
STEP: Creating log watcher for controller kube-system/kube-controller-manager-md-scale-k2uqz6-control-plane-d9q4v, container kube-controller-manager
STEP: Collecting events for Pod kube-system/kube-proxy-windows-hcwwc
STEP: Collecting events for Pod kube-system/csi-proxy-2vnr6
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-4b799, container coredns
STEP: Collecting events for Pod kube-system/containerd-logger-f6q5m
STEP: Collecting events for Pod kube-system/calico-node-windows-txtz9
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-8w9f5, container coredns
STEP: failed to find events of Pod "etcd-md-scale-k2uqz6-control-plane-d9q4v"
STEP: Creating log watcher for controller kube-system/csi-proxy-fkp9t, container csi-proxy
STEP: Collecting events for Pod kube-system/calico-node-windows-884s7
STEP: Creating log watcher for controller kube-system/calico-node-windows-txtz9, container calico-node-startup
STEP: Creating log watcher for controller kube-system/calico-node-windows-txtz9, container calico-node-felix
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-4b799
STEP: Creating log watcher for controller kube-system/calico-node-t6g7l, container calico-node
STEP: Collecting events for Pod kube-system/csi-proxy-fkp9t
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-8w9f5
STEP: Collecting events for Pod kube-system/kube-scheduler-md-scale-k2uqz6-control-plane-d9q4v
STEP: Creating log watcher for controller kube-system/containerd-logger-4k5dl, container containerd-logger
STEP: failed to find events of Pod "kube-scheduler-md-scale-k2uqz6-control-plane-d9q4v"
STEP: Creating log watcher for controller kube-system/calico-node-windows-884s7, container calico-node-startup
STEP: Fetching activity logs took 3.133735224s
STEP: Dumping all the Cluster API resources in the "md-scale-sbz5o4" namespace
STEP: Deleting cluster md-scale-sbz5o4/md-scale-k2uqz6
STEP: Deleting cluster md-scale-k2uqz6
INFO: Waiting for the Cluster md-scale-sbz5o4/md-scale-k2uqz6 to be deleted
STEP: Waiting for cluster md-scale-k2uqz6 to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-md-scale-k2uqz6-control-plane-d9q4v, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-z2kz8, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-8w9f5, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-md-scale-k2uqz6-control-plane-d9q4v, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-884s7, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-t6g7l, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-hwp7z, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-fkp9t, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-f6q5m, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-pmpns, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-4k5dl, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-sbfgf, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-txtz9, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-md-scale-k2uqz6-control-plane-d9q4v, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-hcwwc, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-md-scale-k2uqz6-control-plane-d9q4v, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-2vnr6, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-884s7, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-4b799, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-5p9p7, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-txtz9, container calico-node-startup: http2: client connection lost
STEP: Deleting namespace used for hosting the "md-scale" test spec
INFO: Deleting namespace md-scale-sbz5o4
STEP: Redacting sensitive information from logs


• [SLOW TEST:1307.308 seconds]
... skipping 89 lines ...
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-p95wh
STEP: Creating log watcher for controller kube-system/calico-node-ffgsl, container calico-node
STEP: Collecting events for Pod kube-system/kube-proxy-8p4nc
STEP: Collecting events for Pod kube-system/calico-node-ffgsl
STEP: Collecting events for Pod kube-system/kube-scheduler-node-drain-zhpoui-control-plane-vnjlj
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-8kc4x
STEP: Error starting logs stream for pod kube-system/kube-controller-manager-node-drain-zhpoui-control-plane-vnjlj, container kube-controller-manager: pods "node-drain-zhpoui-control-plane-vnjlj" not found
STEP: Error starting logs stream for pod kube-system/kube-proxy-8p4nc, container kube-proxy: pods "node-drain-zhpoui-control-plane-vnjlj" not found
STEP: Error starting logs stream for pod kube-system/etcd-node-drain-zhpoui-control-plane-vnjlj, container etcd: pods "node-drain-zhpoui-control-plane-vnjlj" not found
STEP: Error starting logs stream for pod kube-system/calico-node-mkgb7, container calico-node: pods "node-drain-zhpoui-control-plane-vnjlj" not found
STEP: Error starting logs stream for pod kube-system/kube-apiserver-node-drain-zhpoui-control-plane-vnjlj, container kube-apiserver: pods "node-drain-zhpoui-control-plane-vnjlj" not found
STEP: Error starting logs stream for pod kube-system/kube-scheduler-node-drain-zhpoui-control-plane-vnjlj, container kube-scheduler: pods "node-drain-zhpoui-control-plane-vnjlj" not found
STEP: Fetching activity logs took 2.446745791s
STEP: Dumping all the Cluster API resources in the "node-drain-hox0vj" namespace
STEP: Deleting cluster node-drain-hox0vj/node-drain-zhpoui
STEP: Deleting cluster node-drain-zhpoui
INFO: Waiting for the Cluster node-drain-hox0vj/node-drain-zhpoui to be deleted
STEP: Waiting for cluster node-drain-zhpoui to be deleted
... skipping 11 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 3811.341 seconds
SUCCESS! -- 9 Passed | 0 Failed | 0 Pending | 14 Skipped


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