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

No Test Failures!


Show 9 Passed Tests

Show 14 Skipped Tests

Error lines from build-log.txt

... skipping 517 lines ...
 ✓ Installing CNI 🔌
 • Installing StorageClass 💾  ...
 ✓ Installing StorageClass 💾
INFO: The kubeconfig file for the kind cluster is /tmp/e2e-kind3712014990
INFO: Loading image: "capzci.azurecr.io/cluster-api-azure-controller-amd64:20220903202915"
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-tar66488908/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-tar993335733/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-tar1530620809/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-5bpgz, container manager
STEP: Waiting for deployment capi-kubeadm-control-plane-system/capi-kubeadm-control-plane-controller-manager to be available
... skipping 79 lines ...
Sep  3 20:51:02.501: INFO: Collecting boot logs for AzureMachine quick-start-yg5jp3-md-0-52vhw

Sep  3 20:51:03.051: INFO: Collecting logs for Windows node quick-sta-jkkzp in cluster quick-start-yg5jp3 in namespace quick-start-bi7z20

Sep  3 20:52:34.453: INFO: Collecting boot logs for AzureMachine quick-start-yg5jp3-md-win-jkkzp

Failed to get logs for machine quick-start-yg5jp3-md-win-7db447b666-qvljd, cluster quick-start-bi7z20/quick-start-yg5jp3: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Sep  3 20:52:36.101: INFO: Collecting logs for Windows node quick-sta-8j8rk in cluster quick-start-yg5jp3 in namespace quick-start-bi7z20

Sep  3 20:54:05.873: INFO: Collecting boot logs for AzureMachine quick-start-yg5jp3-md-win-8j8rk

Failed to get logs for machine quick-start-yg5jp3-md-win-7db447b666-xf2qr, cluster quick-start-bi7z20/quick-start-yg5jp3: running command "Get-Content "C:\\cni.log"": Process exited with status 1
STEP: Dumping workload cluster quick-start-bi7z20/quick-start-yg5jp3 kube-system pod logs
STEP: Fetching kube-system pod logs took 1.130219472s
STEP: Dumping workload cluster quick-start-bi7z20/quick-start-yg5jp3 Azure activity log
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-9tctz, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/calico-node-windows-4ck6t
STEP: Creating log watcher for controller kube-system/calico-node-windows-4ck6t, container calico-node-startup
... skipping 7 lines ...
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-v8sfn
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-z6fqx, container coredns
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-9tctz
STEP: Collecting events for Pod kube-system/kube-proxy-windows-tdb9f
STEP: Creating log watcher for controller kube-system/kube-controller-manager-quick-start-yg5jp3-control-plane-txdzs, container kube-controller-manager
STEP: Collecting events for Pod kube-system/kube-controller-manager-quick-start-yg5jp3-control-plane-txdzs
STEP: failed to find events of Pod "kube-controller-manager-quick-start-yg5jp3-control-plane-txdzs"
STEP: Creating log watcher for controller kube-system/kube-proxy-2f6vd, container kube-proxy
STEP: Collecting events for Pod kube-system/calico-node-hk2bn
STEP: Collecting events for Pod kube-system/calico-node-b7ds5
STEP: Creating log watcher for controller kube-system/calico-node-windows-85t6s, container calico-node-felix
STEP: Creating log watcher for controller kube-system/calico-node-hk2bn, container calico-node
STEP: Creating log watcher for controller kube-system/kube-scheduler-quick-start-yg5jp3-control-plane-txdzs, container kube-scheduler
... skipping 8 lines ...
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-xvrpk, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-f456d
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-tdb9f, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-windows-xvrpk
STEP: Collecting events for Pod kube-system/calico-node-windows-85t6s
STEP: Collecting events for Pod kube-system/kube-scheduler-quick-start-yg5jp3-control-plane-txdzs
STEP: failed to find events of Pod "kube-scheduler-quick-start-yg5jp3-control-plane-txdzs"
STEP: Collecting events for Pod kube-system/containerd-logger-zxgnn
STEP: Creating log watcher for controller kube-system/kube-apiserver-quick-start-yg5jp3-control-plane-txdzs, container kube-apiserver
STEP: Collecting events for Pod kube-system/kube-apiserver-quick-start-yg5jp3-control-plane-txdzs
STEP: Collecting events for Pod kube-system/etcd-quick-start-yg5jp3-control-plane-txdzs
STEP: failed to find events of Pod "kube-apiserver-quick-start-yg5jp3-control-plane-txdzs"
STEP: failed to find events of Pod "etcd-quick-start-yg5jp3-control-plane-txdzs"
STEP: Fetching activity logs took 1.187682333s
STEP: Dumping all the Cluster API resources in the "quick-start-bi7z20" namespace
STEP: Deleting cluster quick-start-bi7z20/quick-start-yg5jp3
STEP: Deleting cluster quick-start-yg5jp3
INFO: Waiting for the Cluster quick-start-bi7z20/quick-start-yg5jp3 to be deleted
STEP: Waiting for cluster quick-start-yg5jp3 to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-quick-start-yg5jp3-control-plane-txdzs, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-quick-start-yg5jp3-control-plane-txdzs, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-85t6s, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-z6fqx, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-v896t, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-4ck6t, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-xvrpk, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-hk2bn, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-quick-start-yg5jp3-control-plane-txdzs, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-85t6s, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-f456d, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-tdb9f, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-4ck6t, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-v8sfn, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-2f6vd, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-9tctz, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-bsh2z, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-b7ds5, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-xwxgr, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-zxgnn, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-quick-start-yg5jp3-control-plane-txdzs, container kube-controller-manager: http2: client connection lost
STEP: Deleting namespace used for hosting the "quick-start" test spec
INFO: Deleting namespace quick-start-bi7z20
STEP: Redacting sensitive information from logs


• [SLOW TEST:1069.942 seconds]
... skipping 7 lines ...
Running the Cluster API E2E tests Running the self-hosted spec 
  Should pivot the bootstrap cluster to a self-hosted cluster
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_selfhosted.go:108

STEP: Creating namespace "self-hosted" for hosting the cluster
Sep  3 20:41:20.492: INFO: starting to create namespace for hosting the "self-hosted" test spec
2022/09/03 20:41:20 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-827kqd" 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-827kqd --infrastructure (default) --kubernetes-version v1.22.13 --control-plane-machine-count 1 --worker-machine-count 1 --flavor management
... skipping 69 lines ...
STEP: Collecting events for Pod kube-system/calico-node-h7cb4
STEP: Creating log watcher for controller kube-system/calico-node-xtk8c, container calico-node
STEP: Collecting events for Pod kube-system/calico-node-xtk8c
STEP: Fetching kube-system pod logs took 686.547521ms
STEP: Collecting events for Pod kube-system/etcd-self-hosted-827kqd-control-plane-d5mwj
STEP: Creating log watcher for controller kube-system/kube-apiserver-self-hosted-827kqd-control-plane-d5mwj, container kube-apiserver
STEP: failed to find events of Pod "kube-scheduler-self-hosted-827kqd-control-plane-d5mwj"
STEP: Collecting events for Pod kube-system/kube-proxy-g9fs4
STEP: failed to find events of Pod "etcd-self-hosted-827kqd-control-plane-d5mwj"
STEP: Creating log watcher for controller kube-system/etcd-self-hosted-827kqd-control-plane-d5mwj, container etcd
STEP: Creating log watcher for controller kube-system/kube-controller-manager-self-hosted-827kqd-control-plane-d5mwj, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/kube-proxy-g9fs4, container kube-proxy
STEP: failed to find events of Pod "kube-apiserver-self-hosted-827kqd-control-plane-d5mwj"
STEP: Collecting events for Pod kube-system/kube-proxy-q92fq
STEP: Creating log watcher for controller kube-system/kube-proxy-q92fq, container kube-proxy
STEP: Dumping workload cluster self-hosted/self-hosted-827kqd Azure activity log
STEP: Collecting events for Pod kube-system/kube-controller-manager-self-hosted-827kqd-control-plane-d5mwj
STEP: Creating log watcher for controller kube-system/kube-scheduler-self-hosted-827kqd-control-plane-d5mwj, container kube-scheduler
STEP: failed to find events of Pod "kube-controller-manager-self-hosted-827kqd-control-plane-d5mwj"
STEP: Fetching activity logs took 2.099590258s
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-827kqd
INFO: Waiting for the Cluster self-hosted/self-hosted-827kqd to be deleted
STEP: Waiting for cluster self-hosted-827kqd to be deleted
... skipping 78 lines ...
Sep  3 20:56:33.986: INFO: Collecting boot logs for AzureMachine md-rollout-vsekl5-md-0-lpg6h1-clk5l

Sep  3 20:56:34.527: INFO: Collecting logs for Windows node md-rollou-wd6jk in cluster md-rollout-vsekl5 in namespace md-rollout-pqb7es

Sep  3 20:58:03.582: INFO: Collecting boot logs for AzureMachine md-rollout-vsekl5-md-win-1ei1gx-wd6jk

Failed to get logs for machine md-rollout-vsekl5-md-win-6489d89b69-vfj76, cluster md-rollout-pqb7es/md-rollout-vsekl5: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Sep  3 20:58:04.007: INFO: Collecting logs for Windows node md-rollou-9z5s9 in cluster md-rollout-vsekl5 in namespace md-rollout-pqb7es

Sep  3 20:59:34.695: INFO: Collecting boot logs for AzureMachine md-rollout-vsekl5-md-win-9z5s9

Failed to get logs for machine md-rollout-vsekl5-md-win-d8756bc79-mhs29, cluster md-rollout-pqb7es/md-rollout-vsekl5: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Failed to get logs for machine md-rollout-vsekl5-md-win-d8756bc79-mwbrp, cluster md-rollout-pqb7es/md-rollout-vsekl5: azuremachines.infrastructure.cluster.x-k8s.io "md-rollout-vsekl5-md-win-8nfgb" not found
STEP: Dumping workload cluster md-rollout-pqb7es/md-rollout-vsekl5 kube-system pod logs
STEP: Creating log watcher for controller kube-system/calico-node-rk9rw, container calico-node
STEP: Collecting events for Pod kube-system/calico-node-rk9rw
STEP: Creating log watcher for controller kube-system/calico-node-windows-ksk7s, container calico-node-startup
STEP: Creating log watcher for controller kube-system/calico-node-windows-r2rpf, container calico-node-startup
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-t569j
... skipping 19 lines ...
STEP: Creating log watcher for controller kube-system/csi-proxy-dxv7m, container csi-proxy
STEP: Creating log watcher for controller kube-system/calico-node-windows-pg9tn, container calico-node-startup
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-pjckx
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-x5lwz, container coredns
STEP: Creating log watcher for controller kube-system/etcd-md-rollout-vsekl5-control-plane-f7qr6, container etcd
STEP: Collecting events for Pod kube-system/kube-apiserver-md-rollout-vsekl5-control-plane-f7qr6
STEP: failed to find events of Pod "kube-apiserver-md-rollout-vsekl5-control-plane-f7qr6"
STEP: Collecting events for Pod kube-system/kube-controller-manager-md-rollout-vsekl5-control-plane-f7qr6
STEP: Collecting events for Pod kube-system/csi-proxy-dxv7m
STEP: Collecting events for Pod kube-system/etcd-md-rollout-vsekl5-control-plane-f7qr6
STEP: failed to find events of Pod "etcd-md-rollout-vsekl5-control-plane-f7qr6"
STEP: Creating log watcher for controller kube-system/kube-proxy-bdv84, container kube-proxy
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-x5lwz
STEP: Creating log watcher for controller kube-system/csi-proxy-b82k6, container csi-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-bdv84
STEP: Fetching kube-system pod logs took 1.175051054s
STEP: Dumping workload cluster md-rollout-pqb7es/md-rollout-vsekl5 Azure activity log
... skipping 4 lines ...
STEP: Creating log watcher for controller kube-system/kube-proxy-c4l7n, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-windows-z56sz
STEP: Creating log watcher for controller kube-system/kube-scheduler-md-rollout-vsekl5-control-plane-f7qr6, container kube-scheduler
STEP: Collecting events for Pod kube-system/kube-proxy-windows-zg9fb
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-l29kc, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-scheduler-md-rollout-vsekl5-control-plane-f7qr6
STEP: failed to find events of Pod "kube-scheduler-md-rollout-vsekl5-control-plane-f7qr6"
STEP: Error starting logs stream for pod kube-system/containerd-logger-4dsz9, container containerd-logger: container "containerd-logger" in pod "containerd-logger-4dsz9" is waiting to start: ContainerCreating
STEP: Error starting logs stream for pod kube-system/calico-node-windows-ksk7s, container calico-node-felix: container "calico-node-felix" in pod "calico-node-windows-ksk7s" is waiting to start: PodInitializing
STEP: Error starting logs stream for pod kube-system/calico-node-windows-ksk7s, container calico-node-startup: container "calico-node-startup" in pod "calico-node-windows-ksk7s" is waiting to start: PodInitializing
STEP: Fetching activity logs took 2.358565053s
STEP: Dumping all the Cluster API resources in the "md-rollout-pqb7es" namespace
STEP: Deleting cluster md-rollout-pqb7es/md-rollout-vsekl5
STEP: Deleting cluster md-rollout-vsekl5
INFO: Waiting for the Cluster md-rollout-pqb7es/md-rollout-vsekl5 to be deleted
STEP: Waiting for cluster md-rollout-vsekl5 to be deleted
STEP: Got error while streaming logs for pod kube-system/containerd-logger-57pvg, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-fql6p, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-dxv7m, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-pjckx, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-md-rollout-vsekl5-control-plane-f7qr6, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-r2rpf, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-t569j, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-md-rollout-vsekl5-control-plane-f7qr6, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-b82k6, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-f9q8m, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-z56sz, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-x5lwz, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-l29kc, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-pg9tn, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-zg9fb, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-pg9tn, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-r2rpf, container calico-node-startup: http2: client connection lost
STEP: Deleting namespace used for hosting the "md-rollout" test spec
INFO: Deleting namespace md-rollout-pqb7es
STEP: Redacting sensitive information from logs


• [SLOW TEST:1663.327 seconds]
... skipping 64 lines ...
STEP: Dumping workload cluster mhc-remediation-7v44g4/mhc-remediation-v0s92v Azure activity log
STEP: Creating log watcher for controller kube-system/etcd-mhc-remediation-v0s92v-control-plane-sptwg, container etcd
STEP: Collecting events for Pod kube-system/kube-controller-manager-mhc-remediation-v0s92v-control-plane-sptwg
STEP: Collecting events for Pod kube-system/kube-proxy-d6m6r
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-tk6wc, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/kube-apiserver-mhc-remediation-v0s92v-control-plane-sptwg
STEP: failed to find events of Pod "kube-controller-manager-mhc-remediation-v0s92v-control-plane-sptwg"
STEP: Creating log watcher for controller kube-system/kube-controller-manager-mhc-remediation-v0s92v-control-plane-sptwg, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/calico-node-9zcsc, container calico-node
STEP: failed to find events of Pod "kube-apiserver-mhc-remediation-v0s92v-control-plane-sptwg"
STEP: Collecting events for Pod kube-system/kube-scheduler-mhc-remediation-v0s92v-control-plane-sptwg
STEP: failed to find events of Pod "kube-scheduler-mhc-remediation-v0s92v-control-plane-sptwg"
STEP: Creating log watcher for controller kube-system/calico-node-nqrh8, container calico-node
STEP: Creating log watcher for controller kube-system/kube-scheduler-mhc-remediation-v0s92v-control-plane-sptwg, container kube-scheduler
STEP: Collecting events for Pod kube-system/kube-proxy-qc2wn
STEP: Creating log watcher for controller kube-system/kube-apiserver-mhc-remediation-v0s92v-control-plane-sptwg, container kube-apiserver
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-8nh8m
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-np6dl, container coredns
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-8nh8m, container coredns
STEP: Creating log watcher for controller kube-system/kube-proxy-qc2wn, container kube-proxy
STEP: Collecting events for Pod kube-system/etcd-mhc-remediation-v0s92v-control-plane-sptwg
STEP: failed to find events of Pod "etcd-mhc-remediation-v0s92v-control-plane-sptwg"
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-tk6wc
STEP: Collecting events for Pod kube-system/calico-node-nqrh8
STEP: Creating log watcher for controller kube-system/kube-proxy-d6m6r, container kube-proxy
STEP: Fetching activity logs took 1.56624272s
STEP: Dumping all the Cluster API resources in the "mhc-remediation-7v44g4" namespace
STEP: Deleting cluster mhc-remediation-7v44g4/mhc-remediation-v0s92v
... skipping 76 lines ...
STEP: Fetching activity logs took 1.471757497s
STEP: Dumping all the Cluster API resources in the "kcp-adoption-txerse" namespace
STEP: Deleting cluster kcp-adoption-txerse/kcp-adoption-th0vmg
STEP: Deleting cluster kcp-adoption-th0vmg
INFO: Waiting for the Cluster kcp-adoption-txerse/kcp-adoption-th0vmg to be deleted
STEP: Waiting for cluster kcp-adoption-th0vmg to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-proxy-4755s, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-kcp-adoption-th0vmg-control-plane-0, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-kcp-adoption-th0vmg-control-plane-0, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-xkb2p, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-kcp-adoption-th0vmg-control-plane-0, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-kcp-adoption-th0vmg-control-plane-0, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-dgjlb, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-gwxkr, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-44mn9, container coredns: http2: client connection lost
STEP: Deleting namespace used for hosting the "kcp-adoption" test spec
INFO: Deleting namespace kcp-adoption-txerse
STEP: Redacting sensitive information from logs


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


• [SLOW TEST:1396.186 seconds]
... skipping 74 lines ...
STEP: Collecting events for Pod kube-system/kube-apiserver-machine-pool-fixbb6-control-plane-qp5g5
STEP: Creating log watcher for controller kube-system/calico-node-7ts2t, container calico-node
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-62pl5, container coredns
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-62pl5
STEP: Creating log watcher for controller kube-system/etcd-machine-pool-fixbb6-control-plane-qp5g5, container etcd
STEP: Collecting events for Pod kube-system/etcd-machine-pool-fixbb6-control-plane-qp5g5
STEP: failed to find events of Pod "etcd-machine-pool-fixbb6-control-plane-qp5g5"
STEP: Creating log watcher for controller kube-system/kube-apiserver-machine-pool-fixbb6-control-plane-qp5g5, container kube-apiserver
STEP: Creating log watcher for controller kube-system/calico-node-l9vwj, container calico-node
STEP: Creating log watcher for controller kube-system/kube-controller-manager-machine-pool-fixbb6-control-plane-qp5g5, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/calico-node-windows-g59cc, container calico-node-felix
STEP: Collecting events for Pod kube-system/calico-node-windows-g59cc
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-6lrbh, container coredns
STEP: Collecting events for Pod kube-system/calico-node-l9vwj
STEP: Creating log watcher for controller kube-system/calico-node-wtbx9, container calico-node
STEP: Collecting events for Pod kube-system/calico-node-7ts2t
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-6lrbh
STEP: Collecting events for Pod kube-system/kube-controller-manager-machine-pool-fixbb6-control-plane-qp5g5
STEP: failed to find events of Pod "kube-controller-manager-machine-pool-fixbb6-control-plane-qp5g5"
STEP: Creating log watcher for controller kube-system/kube-proxy-5mfck, container kube-proxy
STEP: Collecting events for Pod kube-system/calico-node-wtbx9
STEP: Collecting events for Pod kube-system/kube-proxy-rw27h
STEP: Collecting events for Pod kube-system/kube-proxy-b7r4s
STEP: Creating log watcher for controller kube-system/kube-scheduler-machine-pool-fixbb6-control-plane-qp5g5, container kube-scheduler
STEP: Creating log watcher for controller kube-system/kube-proxy-gqr7n, container kube-proxy
... skipping 2 lines ...
STEP: Creating log watcher for controller kube-system/kube-proxy-b7r4s, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-gqr7n
STEP: Collecting events for Pod kube-system/kube-proxy-windows-vf2rv
STEP: Creating log watcher for controller kube-system/kube-proxy-rw27h, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-vf2rv, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-scheduler-machine-pool-fixbb6-control-plane-qp5g5
STEP: Error starting logs stream for pod kube-system/calico-node-windows-g59cc, container calico-node-felix: pods "win-p-win000002" not found
STEP: Error starting logs stream for pod kube-system/kube-proxy-windows-vf2rv, container kube-proxy: pods "win-p-win000002" not found
STEP: Error starting logs stream for pod kube-system/calico-node-windows-g59cc, container calico-node-startup: pods "win-p-win000002" not found
STEP: Fetching activity logs took 2.232222295s
STEP: Dumping all the Cluster API resources in the "machine-pool-3xef6p" namespace
STEP: Deleting cluster machine-pool-3xef6p/machine-pool-fixbb6
STEP: Deleting cluster machine-pool-fixbb6
INFO: Waiting for the Cluster machine-pool-3xef6p/machine-pool-fixbb6 to be deleted
STEP: Waiting for cluster machine-pool-fixbb6 to be deleted
STEP: Error starting logs stream for pod kube-system/calico-node-89s9d, container calico-node: Get "https://10.1.0.5:10250/containerLogs/kube-system/calico-node-89s9d/calico-node?follow=true": dial tcp 10.1.0.5:10250: i/o timeout
STEP: Error starting logs stream for pod kube-system/calico-node-wtbx9, container calico-node: Get "https://10.1.0.8:10250/containerLogs/kube-system/calico-node-wtbx9/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-b7r4s, container kube-proxy: Get "https://10.1.0.4:10250/containerLogs/kube-system/kube-proxy-b7r4s/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-rw27h, container kube-proxy: Get "https://10.1.0.5:10250/containerLogs/kube-system/kube-proxy-rw27h/kube-proxy?follow=true": dial tcp 10.1.0.5:10250: i/o timeout
STEP: Error starting logs stream for pod kube-system/kube-proxy-gqr7n, container kube-proxy: Get "https://10.1.0.8:10250/containerLogs/kube-system/kube-proxy-gqr7n/kube-proxy?follow=true": dial tcp 10.1.0.8:10250: i/o timeout
STEP: Error starting logs stream for pod kube-system/calico-node-7ts2t, container calico-node: Get "https://10.1.0.4:10250/containerLogs/kube-system/calico-node-7ts2t/calico-node?follow=true": dial tcp 10.1.0.4:10250: i/o timeout
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-62pl5, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-5mfck, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-machine-pool-fixbb6-control-plane-qp5g5, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-machine-pool-fixbb6-control-plane-qp5g5, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-machine-pool-fixbb6-control-plane-qp5g5, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-l9vwj, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-snhcj, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-6lrbh, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-machine-pool-fixbb6-control-plane-qp5g5, container kube-apiserver: http2: client connection lost
STEP: Deleting namespace used for hosting the "machine-pool" test spec
INFO: Deleting namespace machine-pool-3xef6p
STEP: Redacting sensitive information from logs


• [SLOW TEST:1370.946 seconds]
... skipping 67 lines ...
Sep  3 21:32:48.982: INFO: Collecting boot logs for AzureMachine md-scale-zchk9p-md-0-kx4cv

Sep  3 21:32:49.557: INFO: Collecting logs for Windows node md-scale-98m9k in cluster md-scale-zchk9p in namespace md-scale-rksz4n

Sep  3 21:34:24.750: INFO: Collecting boot logs for AzureMachine md-scale-zchk9p-md-win-98m9k

Failed to get logs for machine md-scale-zchk9p-md-win-5d8d666db9-g6cfr, cluster md-scale-rksz4n/md-scale-zchk9p: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Sep  3 21:34:25.835: INFO: Collecting logs for Windows node md-scale-8rc7s in cluster md-scale-zchk9p in namespace md-scale-rksz4n

Sep  3 21:36:01.233: INFO: Collecting boot logs for AzureMachine md-scale-zchk9p-md-win-8rc7s

Failed to get logs for machine md-scale-zchk9p-md-win-5d8d666db9-hng9j, cluster md-scale-rksz4n/md-scale-zchk9p: running command "Get-Content "C:\\cni.log"": Process exited with status 1
STEP: Dumping workload cluster md-scale-rksz4n/md-scale-zchk9p kube-system pod logs
STEP: Collecting events for Pod kube-system/calico-node-windows-gcx7x
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-6t226, container coredns
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-6n29v, container calico-kube-controllers
STEP: Fetching kube-system pod logs took 1.139768104s
STEP: Dumping workload cluster md-scale-rksz4n/md-scale-zchk9p Azure activity log
... skipping 5 lines ...
STEP: Creating log watcher for controller kube-system/calico-node-82rn6, container calico-node
STEP: Creating log watcher for controller kube-system/calico-node-windows-gcx7x, container calico-node-felix
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-6n29v
STEP: Creating log watcher for controller kube-system/calico-node-windows-2dxnf, container calico-node-felix
STEP: Collecting events for Pod kube-system/calico-node-82rn6
STEP: Collecting events for Pod kube-system/kube-controller-manager-md-scale-zchk9p-control-plane-wfdtx
STEP: failed to find events of Pod "kube-controller-manager-md-scale-zchk9p-control-plane-wfdtx"
STEP: Collecting events for Pod kube-system/csi-proxy-28xgb
STEP: Creating log watcher for controller kube-system/csi-proxy-wthxt, container csi-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-bmsgl, container kube-proxy
STEP: failed to find events of Pod "kube-scheduler-md-scale-zchk9p-control-plane-wfdtx"
STEP: Creating log watcher for controller kube-system/containerd-logger-cqh98, container containerd-logger
STEP: Collecting events for Pod kube-system/calico-node-windows-2dxnf
STEP: Collecting events for Pod kube-system/etcd-md-scale-zchk9p-control-plane-wfdtx
STEP: Creating log watcher for controller kube-system/calico-node-l8kmc, container calico-node
STEP: failed to find events of Pod "etcd-md-scale-zchk9p-control-plane-wfdtx"
STEP: Collecting events for Pod kube-system/csi-proxy-wthxt
STEP: Creating log watcher for controller kube-system/etcd-md-scale-zchk9p-control-plane-wfdtx, container etcd
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-ndplg, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-tftdx, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-apiserver-md-scale-zchk9p-control-plane-wfdtx, container kube-apiserver
STEP: Collecting events for Pod kube-system/kube-proxy-windows-tftdx
... skipping 6 lines ...
STEP: Collecting events for Pod kube-system/kube-proxy-mx5hc
STEP: Collecting events for Pod kube-system/kube-proxy-windows-ndplg
STEP: Collecting events for Pod kube-system/kube-proxy-bmsgl
STEP: Collecting events for Pod kube-system/containerd-logger-pw4ws
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-sgstr, container coredns
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-sgstr
STEP: failed to find events of Pod "kube-apiserver-md-scale-zchk9p-control-plane-wfdtx"
STEP: Collecting events for Pod kube-system/calico-node-l8kmc
STEP: Fetching activity logs took 3.848992459s
STEP: Dumping all the Cluster API resources in the "md-scale-rksz4n" namespace
STEP: Deleting cluster md-scale-rksz4n/md-scale-zchk9p
STEP: Deleting cluster md-scale-zchk9p
INFO: Waiting for the Cluster md-scale-rksz4n/md-scale-zchk9p to be deleted
STEP: Waiting for cluster md-scale-zchk9p to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-md-scale-zchk9p-control-plane-wfdtx, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-md-scale-zchk9p-control-plane-wfdtx, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-wthxt, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-bmsgl, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-6t226, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-md-scale-zchk9p-control-plane-wfdtx, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-ndplg, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-l8kmc, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-2dxnf, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-2dxnf, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-gcx7x, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-82rn6, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-gcx7x, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-cqh98, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-tftdx, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-md-scale-zchk9p-control-plane-wfdtx, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-28xgb, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-mx5hc, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-6n29v, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-sgstr, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-pw4ws, container containerd-logger: http2: client connection lost
STEP: Deleting namespace used for hosting the "md-scale" test spec
INFO: Deleting namespace md-scale-rksz4n
STEP: Redacting sensitive information from logs


• [SLOW TEST:1320.536 seconds]
... skipping 89 lines ...
STEP: Collecting events for Pod kube-system/kube-scheduler-node-drain-iyxoqc-control-plane-csdpz
STEP: Collecting events for Pod kube-system/calico-node-tnhh7
STEP: Creating log watcher for controller kube-system/kube-proxy-5lr26, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-controller-manager-node-drain-iyxoqc-control-plane-x4qzq
STEP: Collecting events for Pod kube-system/kube-proxy-5lr26
STEP: Creating log watcher for controller kube-system/kube-proxy-9prfm, container kube-proxy
STEP: Error starting logs stream for pod kube-system/calico-node-tnhh7, container calico-node: pods "node-drain-iyxoqc-control-plane-csdpz" not found
STEP: Error starting logs stream for pod kube-system/etcd-node-drain-iyxoqc-control-plane-csdpz, container etcd: pods "node-drain-iyxoqc-control-plane-csdpz" not found
STEP: Error starting logs stream for pod kube-system/kube-controller-manager-node-drain-iyxoqc-control-plane-csdpz, container kube-controller-manager: pods "node-drain-iyxoqc-control-plane-csdpz" not found
STEP: Error starting logs stream for pod kube-system/kube-scheduler-node-drain-iyxoqc-control-plane-csdpz, container kube-scheduler: pods "node-drain-iyxoqc-control-plane-csdpz" not found
STEP: Error starting logs stream for pod kube-system/kube-proxy-9prfm, container kube-proxy: pods "node-drain-iyxoqc-control-plane-csdpz" not found
STEP: Error starting logs stream for pod kube-system/kube-apiserver-node-drain-iyxoqc-control-plane-csdpz, container kube-apiserver: pods "node-drain-iyxoqc-control-plane-csdpz" not found
STEP: Fetching activity logs took 4.200066235s
STEP: Dumping all the Cluster API resources in the "node-drain-kbg61q" namespace
STEP: Deleting cluster node-drain-kbg61q/node-drain-iyxoqc
STEP: Deleting cluster node-drain-iyxoqc
INFO: Waiting for the Cluster node-drain-kbg61q/node-drain-iyxoqc to be deleted
STEP: Waiting for cluster node-drain-iyxoqc 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 4211.506 seconds
SUCCESS! -- 9 Passed | 0 Failed | 0 Pending | 14 Skipped


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