This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 8 succeeded
Started2022-09-08 20:30
Elapsed1h35m
Revisionrelease-1.4

Test Failures


capz-e2e Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger KCP remediation 31m3s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sRunning\sthe\sCluster\sAPI\sE2E\stests\sShould\ssuccessfully\sremediate\sunhealthy\smachines\swith\sMachineHealthCheck\sShould\ssuccessfully\strigger\sKCP\sremediation$'
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.4/e2e/mhc_remediations.go:114
Timed out after 1200.002s.
Expected
    <int>: 1
to equal
    <int>: 3
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.4/framework/controlplane_helpers.go:114
				
				Click to see stdout/stderrfrom junit.e2e_suite.2.xml

Filter through log files | View test history on testgrid


Show 8 Passed Tests

Show 14 Skipped Tests

Error lines from build-log.txt

... skipping 521 lines ...
 ✓ Installing CNI 🔌
 • Installing StorageClass 💾  ...
 ✓ Installing StorageClass 💾
INFO: The kubeconfig file for the kind cluster is /tmp/e2e-kind204708096
INFO: Loading image: "capzci.azurecr.io/cluster-api-azure-controller-amd64:20220908203121"
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-tar2252817820/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-tar3639317007/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-tar3169482099/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-8slmh, 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  8 20:42:44.308: INFO: starting to create namespace for hosting the "self-hosted" test spec
2022/09/08 20:42:44 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-xfuy6q" 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-xfuy6q --infrastructure (default) --kubernetes-version v1.22.13 --control-plane-machine-count 1 --worker-machine-count 1 --flavor management
... skipping 59 lines ...
STEP: Dumping workload cluster self-hosted/self-hosted-xfuy6q kube-system pod logs
STEP: Fetching kube-system pod logs took 700.966689ms
STEP: Dumping workload cluster self-hosted/self-hosted-xfuy6q Azure activity log
STEP: Creating log watcher for controller kube-system/etcd-self-hosted-xfuy6q-control-plane-lzv4t, container etcd
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-khsqg, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/kube-controller-manager-self-hosted-xfuy6q-control-plane-lzv4t
STEP: failed to find events of Pod "kube-controller-manager-self-hosted-xfuy6q-control-plane-lzv4t"
STEP: Collecting events for Pod kube-system/etcd-self-hosted-xfuy6q-control-plane-lzv4t
STEP: failed to find events of Pod "etcd-self-hosted-xfuy6q-control-plane-lzv4t"
STEP: Creating log watcher for controller kube-system/kube-apiserver-self-hosted-xfuy6q-control-plane-lzv4t, container kube-apiserver
STEP: Creating log watcher for controller kube-system/kube-proxy-46z6r, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-wjw55
STEP: Collecting events for Pod kube-system/kube-apiserver-self-hosted-xfuy6q-control-plane-lzv4t
STEP: Collecting events for Pod kube-system/kube-proxy-46z6r
STEP: failed to find events of Pod "kube-apiserver-self-hosted-xfuy6q-control-plane-lzv4t"
STEP: Collecting events for Pod kube-system/kube-scheduler-self-hosted-xfuy6q-control-plane-lzv4t
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-khsqg
STEP: Creating log watcher for controller kube-system/kube-proxy-wjw55, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-controller-manager-self-hosted-xfuy6q-control-plane-lzv4t, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-wrxgj, container coredns
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-qrb85
STEP: Creating log watcher for controller kube-system/calico-node-k25vk, container calico-node
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-wrxgj
STEP: Creating log watcher for controller kube-system/kube-scheduler-self-hosted-xfuy6q-control-plane-lzv4t, container kube-scheduler
STEP: Collecting events for Pod kube-system/calico-node-k25vk
STEP: Creating log watcher for controller kube-system/calico-node-z9jmk, container calico-node
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-qrb85, container coredns
STEP: Collecting events for Pod kube-system/calico-node-z9jmk
STEP: failed to find events of Pod "kube-scheduler-self-hosted-xfuy6q-control-plane-lzv4t"
STEP: Fetching activity logs took 2.486045239s
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-xfuy6q
INFO: Waiting for the Cluster self-hosted/self-hosted-xfuy6q to be deleted
STEP: Waiting for cluster self-hosted-xfuy6q to be deleted
... skipping 67 lines ...
Sep  8 20:51:28.889: INFO: Collecting boot logs for AzureMachine quick-start-wu0gxo-md-0-zrxl9

Sep  8 20:51:29.545: INFO: Collecting logs for Windows node quick-sta-h8f8v in cluster quick-start-wu0gxo in namespace quick-start-xxwbp0

Sep  8 20:52:59.014: INFO: Collecting boot logs for AzureMachine quick-start-wu0gxo-md-win-h8f8v

Failed to get logs for machine quick-start-wu0gxo-md-win-c78d7d684-8dpmj, cluster quick-start-xxwbp0/quick-start-wu0gxo: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Sep  8 20:52:59.644: INFO: Collecting logs for Windows node quick-sta-xp9nh in cluster quick-start-wu0gxo in namespace quick-start-xxwbp0

Sep  8 20:54:32.262: INFO: Collecting boot logs for AzureMachine quick-start-wu0gxo-md-win-xp9nh

Failed to get logs for machine quick-start-wu0gxo-md-win-c78d7d684-8h6gf, cluster quick-start-xxwbp0/quick-start-wu0gxo: running command "Get-Content "C:\\cni.log"": Process exited with status 1
STEP: Dumping workload cluster quick-start-xxwbp0/quick-start-wu0gxo kube-system pod logs
STEP: Fetching kube-system pod logs took 1.153347571s
STEP: Dumping workload cluster quick-start-xxwbp0/quick-start-wu0gxo Azure activity log
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-ndf56
STEP: Creating log watcher for controller kube-system/csi-proxy-8ppqv, container csi-proxy
STEP: Creating log watcher for controller kube-system/csi-proxy-dqqk9, container csi-proxy
STEP: Creating log watcher for controller kube-system/kube-apiserver-quick-start-wu0gxo-control-plane-9zktr, container kube-apiserver
STEP: Collecting events for Pod kube-system/kube-controller-manager-quick-start-wu0gxo-control-plane-9zktr
STEP: Collecting events for Pod kube-system/etcd-quick-start-wu0gxo-control-plane-9zktr
STEP: Collecting events for Pod kube-system/kube-apiserver-quick-start-wu0gxo-control-plane-9zktr
STEP: failed to find events of Pod "kube-apiserver-quick-start-wu0gxo-control-plane-9zktr"
STEP: Creating log watcher for controller kube-system/calico-node-windows-j4c6l, container calico-node-startup
STEP: failed to find events of Pod "etcd-quick-start-wu0gxo-control-plane-9zktr"
STEP: Creating log watcher for controller kube-system/containerd-logger-xgnr4, container containerd-logger
STEP: Creating log watcher for controller kube-system/kube-proxy-fmsbg, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-controller-manager-quick-start-wu0gxo-control-plane-9zktr, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/calico-node-windows-j4c6l, container calico-node-felix
STEP: Creating log watcher for controller kube-system/etcd-quick-start-wu0gxo-control-plane-9zktr, container etcd
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-cn4jn, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/kube-proxy-fmsbg
STEP: Collecting events for Pod kube-system/calico-node-w82gz
STEP: Creating log watcher for controller kube-system/kube-proxy-gnpmz, container kube-proxy
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-cn4jn
STEP: Creating log watcher for controller kube-system/calico-node-sp4kt, container calico-node
STEP: Collecting events for Pod kube-system/calico-node-windows-j4c6l
STEP: Creating log watcher for controller kube-system/containerd-logger-qgdz5, container containerd-logger
STEP: failed to find events of Pod "kube-controller-manager-quick-start-wu0gxo-control-plane-9zktr"
STEP: Collecting events for Pod kube-system/csi-proxy-8ppqv
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-trftn, container kube-proxy
STEP: Collecting events for Pod kube-system/containerd-logger-xgnr4
STEP: Creating log watcher for controller kube-system/calico-node-windows-282b6, container calico-node-startup
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-cf6dc, container coredns
STEP: Collecting events for Pod kube-system/calico-node-sp4kt
STEP: Creating log watcher for controller kube-system/calico-node-w82gz, container calico-node
STEP: Collecting events for Pod kube-system/kube-proxy-windows-trftn
STEP: Creating log watcher for controller kube-system/kube-scheduler-quick-start-wu0gxo-control-plane-9zktr, container kube-scheduler
STEP: Collecting events for Pod kube-system/kube-scheduler-quick-start-wu0gxo-control-plane-9zktr
STEP: failed to find events of Pod "kube-scheduler-quick-start-wu0gxo-control-plane-9zktr"
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-cf6dc
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-776s9, container kube-proxy
STEP: Collecting events for Pod kube-system/containerd-logger-qgdz5
STEP: Collecting events for Pod kube-system/kube-proxy-windows-776s9
STEP: Collecting events for Pod kube-system/calico-node-windows-282b6
STEP: Collecting events for Pod kube-system/kube-proxy-gnpmz
STEP: Creating log watcher for controller kube-system/calico-node-windows-282b6, container calico-node-felix
STEP: Collecting events for Pod kube-system/csi-proxy-dqqk9
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-ndf56, container coredns
STEP: Error fetching activity logs for resource group capz-e2e-4nsncy: insights.ActivityLogsClient#List: Failure sending request: StatusCode=0 -- Original Error: context deadline exceeded
STEP: Fetching activity logs took 30.001879667s
STEP: Dumping all the Cluster API resources in the "quick-start-xxwbp0" namespace
STEP: Deleting cluster quick-start-xxwbp0/quick-start-wu0gxo
STEP: Deleting cluster quick-start-wu0gxo
INFO: Waiting for the Cluster quick-start-xxwbp0/quick-start-wu0gxo to be deleted
STEP: Waiting for cluster quick-start-wu0gxo to be deleted
STEP: Got error while streaming logs for pod kube-system/calico-node-sp4kt, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-quick-start-wu0gxo-control-plane-9zktr, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-cf6dc, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-cn4jn, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-quick-start-wu0gxo-control-plane-9zktr, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-gnpmz, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-quick-start-wu0gxo-control-plane-9zktr, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-quick-start-wu0gxo-control-plane-9zktr, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-ndf56, container coredns: http2: client connection lost
STEP: Deleting namespace used for hosting the "quick-start" test spec
INFO: Deleting namespace quick-start-xxwbp0
STEP: Redacting sensitive information from logs


• [SLOW TEST:1245.508 seconds]
... skipping 70 lines ...
Sep  8 20:56:54.844: INFO: Collecting boot logs for AzureMachine md-rollout-zl701f-md-0-ltme1x-nnwgr

Sep  8 20:56:55.368: INFO: Collecting logs for Windows node md-rollou-c4kbx in cluster md-rollout-zl701f in namespace md-rollout-hbee4e

Sep  8 20:58:24.441: INFO: Collecting boot logs for AzureMachine md-rollout-zl701f-md-win-c4kbx

Failed to get logs for machine md-rollout-zl701f-md-win-577c49c9f7-fdlg8, cluster md-rollout-hbee4e/md-rollout-zl701f: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Failed to get logs for machine md-rollout-zl701f-md-win-577c49c9f7-tb2pk, cluster md-rollout-hbee4e/md-rollout-zl701f: azuremachines.infrastructure.cluster.x-k8s.io "md-rollout-zl701f-md-win-6nk6h" not found
Sep  8 20:58:24.840: INFO: Collecting logs for Windows node md-rollou-jvcn6 in cluster md-rollout-zl701f in namespace md-rollout-hbee4e

Sep  8 20:59:55.686: INFO: Collecting boot logs for AzureMachine md-rollout-zl701f-md-win-jzzmxk-jvcn6

Failed to get logs for machine md-rollout-zl701f-md-win-5bdf4bb448-hhm7k, cluster md-rollout-hbee4e/md-rollout-zl701f: running command "Get-Content "C:\\cni.log"": Process exited with status 1
STEP: Dumping workload cluster md-rollout-hbee4e/md-rollout-zl701f kube-system pod logs
STEP: Creating log watcher for controller kube-system/calico-node-windows-k4kqh, container calico-node-startup
STEP: Collecting events for Pod kube-system/kube-scheduler-md-rollout-zl701f-control-plane-nlpvp
STEP: Creating log watcher for controller kube-system/calico-node-mt7lj, container calico-node
STEP: Creating log watcher for controller kube-system/containerd-logger-6cqtj, container containerd-logger
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-rg4lv, container coredns
STEP: failed to find events of Pod "kube-scheduler-md-rollout-zl701f-control-plane-nlpvp"
STEP: Collecting events for Pod kube-system/csi-proxy-qbrhm
STEP: Creating log watcher for controller kube-system/etcd-md-rollout-zl701f-control-plane-nlpvp, container etcd
STEP: Fetching kube-system pod logs took 1.181509043s
STEP: Creating log watcher for controller kube-system/calico-node-h6hfz, container calico-node
STEP: Collecting events for Pod kube-system/calico-node-mt7lj
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-7q8rk, container calico-kube-controllers
STEP: Creating log watcher for controller kube-system/csi-proxy-mxznb, container csi-proxy
STEP: Collecting events for Pod kube-system/etcd-md-rollout-zl701f-control-plane-nlpvp
STEP: failed to find events of Pod "etcd-md-rollout-zl701f-control-plane-nlpvp"
STEP: Creating log watcher for controller kube-system/kube-apiserver-md-rollout-zl701f-control-plane-nlpvp, container kube-apiserver
STEP: Collecting events for Pod kube-system/csi-proxy-mxznb
STEP: Collecting events for Pod kube-system/kube-proxy-windows-nvnqv
STEP: Collecting events for Pod kube-system/kube-apiserver-md-rollout-zl701f-control-plane-nlpvp
STEP: failed to find events of Pod "kube-apiserver-md-rollout-zl701f-control-plane-nlpvp"
STEP: Creating log watcher for controller kube-system/kube-controller-manager-md-rollout-zl701f-control-plane-nlpvp, container kube-controller-manager
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-7q8rk
STEP: Creating log watcher for controller kube-system/calico-node-windows-k4kqh, container calico-node-felix
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-rg4lv
STEP: Creating log watcher for controller kube-system/calico-node-windows-h2nph, container calico-node-startup
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-7jmqk, container kube-proxy
STEP: Collecting events for Pod kube-system/calico-node-windows-k4kqh
STEP: Creating log watcher for controller kube-system/calico-node-windows-kpxcw, container calico-node-startup
STEP: Collecting events for Pod kube-system/kube-controller-manager-md-rollout-zl701f-control-plane-nlpvp
STEP: Collecting events for Pod kube-system/kube-proxy-windows-7jmqk
STEP: failed to find events of Pod "kube-controller-manager-md-rollout-zl701f-control-plane-nlpvp"
STEP: Creating log watcher for controller kube-system/calico-node-windows-h2nph, container calico-node-felix
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-nvnqv, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-ppx4k, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-zflpc
STEP: Collecting events for Pod kube-system/kube-proxy-windows-ppx4k
STEP: Creating log watcher for controller kube-system/kube-proxy-zflpc, container kube-proxy
... skipping 10 lines ...
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-8fvr7
STEP: Collecting events for Pod kube-system/calico-node-h6hfz
STEP: Dumping workload cluster md-rollout-hbee4e/md-rollout-zl701f Azure activity log
STEP: Collecting events for Pod kube-system/containerd-logger-lhhdk
STEP: Collecting events for Pod kube-system/containerd-logger-6cqtj
STEP: Collecting events for Pod kube-system/calico-node-windows-h2nph
STEP: Error starting logs stream for pod kube-system/kube-proxy-windows-ppx4k, container kube-proxy: container "kube-proxy" in pod "kube-proxy-windows-ppx4k" is waiting to start: ContainerCreating
STEP: Error starting logs stream for pod kube-system/calico-node-windows-k4kqh, container calico-node-startup: container "calico-node-startup" in pod "calico-node-windows-k4kqh" is waiting to start: PodInitializing
STEP: Error starting logs stream for pod kube-system/calico-node-windows-k4kqh, container calico-node-felix: container "calico-node-felix" in pod "calico-node-windows-k4kqh" is waiting to start: PodInitializing
STEP: Error starting logs stream for pod kube-system/containerd-logger-4qc6d, container containerd-logger: container "containerd-logger" in pod "containerd-logger-4qc6d" is waiting to start: ContainerCreating
STEP: Fetching activity logs took 2.290777575s
STEP: Dumping all the Cluster API resources in the "md-rollout-hbee4e" namespace
STEP: Deleting cluster md-rollout-hbee4e/md-rollout-zl701f
STEP: Deleting cluster md-rollout-zl701f
INFO: Waiting for the Cluster md-rollout-hbee4e/md-rollout-zl701f to be deleted
STEP: Waiting for cluster md-rollout-zl701f to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-proxy-zkprj, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-lhhdk, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-nvnqv, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-h2nph, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-md-rollout-zl701f-control-plane-nlpvp, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-kpxcw, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-zflpc, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-6cqtj, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-8fvr7, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-mt7lj, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-md-rollout-zl701f-control-plane-nlpvp, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-rg4lv, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-kpxcw, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-h6hfz, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-md-rollout-zl701f-control-plane-nlpvp, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-7q8rk, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-mxznb, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-qbrhm, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-h2nph, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-7jmqk, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-md-rollout-zl701f-control-plane-nlpvp, container kube-controller-manager: http2: client connection lost
STEP: Deleting namespace used for hosting the "md-rollout" test spec
INFO: Deleting namespace md-rollout-hbee4e
STEP: Redacting sensitive information from logs


• [SLOW TEST:1601.547 seconds]
... skipping 50 lines ...
STEP: Creating log watcher for controller kube-system/calico-node-d2smh, container calico-node
STEP: Creating log watcher for controller kube-system/kube-controller-manager-kcp-adoption-0ors7z-control-plane-0, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/kube-scheduler-kcp-adoption-0ors7z-control-plane-0, container kube-scheduler
STEP: Collecting events for Pod kube-system/kube-scheduler-kcp-adoption-0ors7z-control-plane-0
STEP: Collecting events for Pod kube-system/etcd-kcp-adoption-0ors7z-control-plane-0
STEP: Collecting events for Pod kube-system/kube-controller-manager-kcp-adoption-0ors7z-control-plane-0
STEP: failed to find events of Pod "kube-controller-manager-kcp-adoption-0ors7z-control-plane-0"
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-dmjtb, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/calico-node-d2smh
STEP: Collecting events for Pod kube-system/kube-apiserver-kcp-adoption-0ors7z-control-plane-0
STEP: failed to find events of Pod "etcd-kcp-adoption-0ors7z-control-plane-0"
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-vfddd
STEP: Creating log watcher for controller kube-system/etcd-kcp-adoption-0ors7z-control-plane-0, container etcd
STEP: failed to find events of Pod "kube-apiserver-kcp-adoption-0ors7z-control-plane-0"
STEP: failed to find events of Pod "kube-scheduler-kcp-adoption-0ors7z-control-plane-0"
STEP: Creating log watcher for controller kube-system/kube-proxy-fllkk, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-fllkk
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-sqvwf, container coredns
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-sqvwf
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-vfddd, container coredns
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-dmjtb
... skipping 73 lines ...
STEP: Fetching kube-system pod logs took 851.621278ms
STEP: Dumping workload cluster mhc-remediation-3hys4k/mhc-remediation-0etbi4 Azure activity log
STEP: Collecting events for Pod kube-system/kube-scheduler-mhc-remediation-0etbi4-control-plane-n2s29
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-2srsr
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-kkqzb, container calico-kube-controllers
STEP: Creating log watcher for controller kube-system/kube-controller-manager-mhc-remediation-0etbi4-control-plane-n2s29, container kube-controller-manager
STEP: failed to find events of Pod "kube-scheduler-mhc-remediation-0etbi4-control-plane-n2s29"
STEP: Creating log watcher for controller kube-system/calico-node-crz6c, container calico-node
STEP: Collecting events for Pod kube-system/calico-node-crz6c
STEP: Collecting events for Pod kube-system/calico-node-2mv2h
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-kkqzb
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-kq64m, container coredns
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-2srsr, container coredns
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-kq64m
STEP: Creating log watcher for controller kube-system/kube-apiserver-mhc-remediation-0etbi4-control-plane-n2s29, container kube-apiserver
STEP: Collecting events for Pod kube-system/kube-apiserver-mhc-remediation-0etbi4-control-plane-n2s29
STEP: Collecting events for Pod kube-system/kube-proxy-5mdgd
STEP: failed to find events of Pod "kube-apiserver-mhc-remediation-0etbi4-control-plane-n2s29"
STEP: Collecting events for Pod kube-system/kube-controller-manager-mhc-remediation-0etbi4-control-plane-n2s29
STEP: Creating log watcher for controller kube-system/kube-proxy-5mdgd, container kube-proxy
STEP: failed to find events of Pod "kube-controller-manager-mhc-remediation-0etbi4-control-plane-n2s29"
STEP: Collecting events for Pod kube-system/etcd-mhc-remediation-0etbi4-control-plane-n2s29
STEP: Creating log watcher for controller kube-system/etcd-mhc-remediation-0etbi4-control-plane-n2s29, container etcd
STEP: Creating log watcher for controller kube-system/kube-scheduler-mhc-remediation-0etbi4-control-plane-n2s29, container kube-scheduler
STEP: Collecting events for Pod kube-system/kube-proxy-b6rbg
STEP: Creating log watcher for controller kube-system/kube-proxy-b6rbg, container kube-proxy
STEP: failed to find events of Pod "etcd-mhc-remediation-0etbi4-control-plane-n2s29"
STEP: Creating log watcher for controller kube-system/calico-node-2mv2h, container calico-node
STEP: Fetching activity logs took 2.829050111s
STEP: Dumping all the Cluster API resources in the "mhc-remediation-3hys4k" namespace
STEP: Deleting cluster mhc-remediation-3hys4k/mhc-remediation-0etbi4
STEP: Deleting cluster mhc-remediation-0etbi4
INFO: Waiting for the Cluster mhc-remediation-3hys4k/mhc-remediation-0etbi4 to be deleted
STEP: Waiting for cluster mhc-remediation-0etbi4 to be deleted
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-2srsr, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-mhc-remediation-0etbi4-control-plane-n2s29, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-kkqzb, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-b6rbg, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-kq64m, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-mhc-remediation-0etbi4-control-plane-n2s29, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-mhc-remediation-0etbi4-control-plane-n2s29, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-mhc-remediation-0etbi4-control-plane-n2s29, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-crz6c, container calico-node: http2: client connection lost
STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
INFO: Deleting namespace mhc-remediation-3hys4k
STEP: Redacting sensitive information from logs


• [SLOW TEST:1877.467 seconds]
... skipping 52 lines ...

STEP: Dumping workload cluster mhc-remediation-4p7e1f/mhc-remediation-mj1w01 kube-system pod logs
STEP: Fetching kube-system pod logs took 1.208401431s
STEP: Dumping workload cluster mhc-remediation-4p7e1f/mhc-remediation-mj1w01 Azure activity log
STEP: Creating log watcher for controller kube-system/etcd-mhc-remediation-mj1w01-control-plane-7qfqx, container etcd
STEP: Collecting events for Pod kube-system/etcd-mhc-remediation-mj1w01-control-plane-7qfqx
STEP: failed to find events of Pod "etcd-mhc-remediation-mj1w01-control-plane-7qfqx"
STEP: Creating log watcher for controller kube-system/kube-apiserver-mhc-remediation-mj1w01-control-plane-7qfqx, container kube-apiserver
STEP: Creating log watcher for controller kube-system/kube-controller-manager-mhc-remediation-mj1w01-control-plane-7qfqx, container kube-controller-manager
STEP: Collecting events for Pod kube-system/kube-apiserver-mhc-remediation-mj1w01-control-plane-7qfqx
STEP: failed to find events of Pod "kube-apiserver-mhc-remediation-mj1w01-control-plane-7qfqx"
STEP: Creating log watcher for controller kube-system/kube-proxy-hsqp4, container kube-proxy
STEP: Collecting events for Pod kube-system/calico-node-g2blt
STEP: Collecting events for Pod kube-system/kube-proxy-hsqp4
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-2lzzf
STEP: Creating log watcher for controller kube-system/calico-node-g2blt, container calico-node
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-2lzzf, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/kube-controller-manager-mhc-remediation-mj1w01-control-plane-7qfqx
STEP: failed to find events of Pod "kube-controller-manager-mhc-remediation-mj1w01-control-plane-7qfqx"
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-2kq5j
STEP: Creating log watcher for controller kube-system/kube-scheduler-mhc-remediation-mj1w01-control-plane-7qfqx, container kube-scheduler
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-2kq5j, container coredns
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-zrp8s, container coredns
STEP: Collecting events for Pod kube-system/kube-scheduler-mhc-remediation-mj1w01-control-plane-7qfqx
STEP: failed to find events of Pod "kube-scheduler-mhc-remediation-mj1w01-control-plane-7qfqx"
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-zrp8s
STEP: Fetching activity logs took 3.079705893s
STEP: Dumping all the Cluster API resources in the "mhc-remediation-4p7e1f" namespace
STEP: Deleting cluster mhc-remediation-4p7e1f/mhc-remediation-mj1w01
STEP: Deleting cluster mhc-remediation-mj1w01
INFO: Waiting for the Cluster mhc-remediation-4p7e1f/mhc-remediation-mj1w01 to be deleted
STEP: Waiting for cluster mhc-remediation-mj1w01 to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-mhc-remediation-mj1w01-control-plane-7qfqx, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-mhc-remediation-mj1w01-control-plane-7qfqx, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-mhc-remediation-mj1w01-control-plane-7qfqx, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-g2blt, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-2kq5j, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-hsqp4, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-mhc-remediation-mj1w01-control-plane-7qfqx, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-2lzzf, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-zrp8s, container coredns: http2: client connection lost
STEP: Deleting namespace used for hosting the "mhc-remediation" test spec
INFO: Deleting namespace mhc-remediation-4p7e1f
STEP: Redacting sensitive information from logs


• Failure [1863.357 seconds]
... skipping 113 lines ...
Sep  8 21:43:12.024: INFO: Collecting boot logs for AzureMachine md-scale-o1tm06-md-0-zhgr9

Sep  8 21:43:12.545: INFO: Collecting logs for Windows node md-scale-8rpzf in cluster md-scale-o1tm06 in namespace md-scale-iwlwoh

Sep  8 21:44:41.369: INFO: Collecting boot logs for AzureMachine md-scale-o1tm06-md-win-8rpzf

Failed to get logs for machine md-scale-o1tm06-md-win-7d5955bcbc-lntlw, cluster md-scale-iwlwoh/md-scale-o1tm06: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Sep  8 21:44:41.896: INFO: Collecting logs for Windows node md-scale-9qv9b in cluster md-scale-o1tm06 in namespace md-scale-iwlwoh

Sep  8 21:46:11.262: INFO: Collecting boot logs for AzureMachine md-scale-o1tm06-md-win-9qv9b

Failed to get logs for machine md-scale-o1tm06-md-win-7d5955bcbc-qg6qt, cluster md-scale-iwlwoh/md-scale-o1tm06: running command "Get-Content "C:\\cni.log"": Process exited with status 1
STEP: Dumping workload cluster md-scale-iwlwoh/md-scale-o1tm06 kube-system pod logs
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-gnz8b, container calico-kube-controllers
STEP: Creating log watcher for controller kube-system/containerd-logger-s866h, container containerd-logger
STEP: Creating log watcher for controller kube-system/calico-node-windows-7dtnl, container calico-node-felix
STEP: Creating log watcher for controller kube-system/calico-node-wdv26, container calico-node
STEP: Collecting events for Pod kube-system/calico-node-windows-7dtnl
... skipping 6 lines ...
STEP: Creating log watcher for controller kube-system/csi-proxy-6r6xk, container csi-proxy
STEP: Creating log watcher for controller kube-system/calico-node-windows-7sg8l, container calico-node-felix
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-gvzjt
STEP: Collecting events for Pod kube-system/kube-scheduler-md-scale-o1tm06-control-plane-wqrtw
STEP: Collecting events for Pod kube-system/kube-apiserver-md-scale-o1tm06-control-plane-wqrtw
STEP: Collecting events for Pod kube-system/containerd-logger-s866h
STEP: failed to find events of Pod "kube-apiserver-md-scale-o1tm06-control-plane-wqrtw"
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-k58g8, container coredns
STEP: Creating log watcher for controller kube-system/kube-controller-manager-md-scale-o1tm06-control-plane-wqrtw, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-gvzjt, container coredns
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-gnz8b
STEP: Collecting events for Pod kube-system/calico-node-648dh
STEP: Creating log watcher for controller kube-system/calico-node-windows-7sg8l, container calico-node-startup
... skipping 2 lines ...
STEP: Creating log watcher for controller kube-system/csi-proxy-p8ws7, container csi-proxy
STEP: Collecting events for Pod kube-system/csi-proxy-6r6xk
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-k58g8
STEP: Creating log watcher for controller kube-system/etcd-md-scale-o1tm06-control-plane-wqrtw, container etcd
STEP: Collecting events for Pod kube-system/csi-proxy-p8ws7
STEP: Collecting events for Pod kube-system/etcd-md-scale-o1tm06-control-plane-wqrtw
STEP: failed to find events of Pod "etcd-md-scale-o1tm06-control-plane-wqrtw"
STEP: Collecting events for Pod kube-system/kube-proxy-fbbcc
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-ftrzd, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-controller-manager-md-scale-o1tm06-control-plane-wqrtw
STEP: Collecting events for Pod kube-system/kube-proxy-9vt7c
STEP: Creating log watcher for controller kube-system/kube-proxy-fbbcc, container kube-proxy
STEP: failed to find events of Pod "kube-scheduler-md-scale-o1tm06-control-plane-wqrtw"
STEP: Collecting events for Pod kube-system/kube-proxy-windows-ftrzd
STEP: Creating log watcher for controller kube-system/kube-scheduler-md-scale-o1tm06-control-plane-wqrtw, container kube-scheduler
STEP: Creating log watcher for controller kube-system/kube-proxy-9vt7c, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-6lllt, container kube-proxy
STEP: Creating log watcher for controller kube-system/calico-node-648dh, container calico-node
STEP: Collecting events for Pod kube-system/kube-proxy-windows-6lllt
STEP: failed to find events of Pod "kube-controller-manager-md-scale-o1tm06-control-plane-wqrtw"
STEP: Fetching activity logs took 2.208026944s
STEP: Dumping all the Cluster API resources in the "md-scale-iwlwoh" namespace
STEP: Deleting cluster md-scale-iwlwoh/md-scale-o1tm06
STEP: Deleting cluster md-scale-o1tm06
INFO: Waiting for the Cluster md-scale-iwlwoh/md-scale-o1tm06 to be deleted
STEP: Waiting for cluster md-scale-o1tm06 to be deleted
... skipping 83 lines ...
STEP: Creating log watcher for controller kube-system/etcd-machine-pool-1v0udq-control-plane-7zb4f, container etcd
STEP: Creating log watcher for controller kube-system/calico-node-2nqz6, container calico-node
STEP: Collecting events for Pod kube-system/etcd-machine-pool-1v0udq-control-plane-7zb4f
STEP: Collecting events for Pod kube-system/calico-node-2nqz6
STEP: Creating log watcher for controller kube-system/kube-apiserver-machine-pool-1v0udq-control-plane-7zb4f, container kube-apiserver
STEP: Collecting events for Pod kube-system/kube-apiserver-machine-pool-1v0udq-control-plane-7zb4f
STEP: failed to find events of Pod "kube-apiserver-machine-pool-1v0udq-control-plane-7zb4f"
STEP: Creating log watcher for controller kube-system/kube-controller-manager-machine-pool-1v0udq-control-plane-7zb4f, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/calico-node-9zhb7, container calico-node
STEP: Collecting events for Pod kube-system/kube-controller-manager-machine-pool-1v0udq-control-plane-7zb4f
STEP: Collecting events for Pod kube-system/calico-node-9zhb7
STEP: Creating log watcher for controller kube-system/kube-proxy-mkvw2, container kube-proxy
STEP: Creating log watcher for controller kube-system/calico-node-crzqz, container calico-node
... skipping 13 lines ...
STEP: Fetching activity logs took 1.962633861s
STEP: Dumping all the Cluster API resources in the "machine-pool-hb5sz1" namespace
STEP: Deleting cluster machine-pool-hb5sz1/machine-pool-1v0udq
STEP: Deleting cluster machine-pool-1v0udq
INFO: Waiting for the Cluster machine-pool-hb5sz1/machine-pool-1v0udq to be deleted
STEP: Waiting for cluster machine-pool-1v0udq to be deleted
STEP: Error starting logs stream for pod kube-system/kube-proxy-4glg8, container kube-proxy: Get "https://10.1.0.9:10250/containerLogs/kube-system/kube-proxy-4glg8/kube-proxy?follow=true": dial tcp 10.1.0.9:10250: i/o timeout
STEP: Error starting logs stream for pod kube-system/kube-proxy-l78qf, container kube-proxy: Get "https://10.1.0.5:10250/containerLogs/kube-system/kube-proxy-l78qf/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-mkvw2, container kube-proxy: Get "https://10.1.0.4:10250/containerLogs/kube-system/kube-proxy-mkvw2/kube-proxy?follow=true": dial tcp 10.1.0.4:10250: i/o timeout
STEP: Error starting logs stream for pod kube-system/calico-node-crzqz, container calico-node: Get "https://10.1.0.9:10250/containerLogs/kube-system/calico-node-crzqz/calico-node?follow=true": dial tcp 10.1.0.9:10250: i/o timeout
STEP: Error starting logs stream for pod kube-system/calico-node-w7wlk, container calico-node: Get "https://10.1.0.5:10250/containerLogs/kube-system/calico-node-w7wlk/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-9zhb7, container calico-node: Get "https://10.1.0.4:10250/containerLogs/kube-system/calico-node-9zhb7/calico-node?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-7fd8h, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-q7n7p, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-machine-pool-1v0udq-control-plane-7zb4f, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-md8dd, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-machine-pool-1v0udq-control-plane-7zb4f, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-hqblf, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-2nqz6, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-machine-pool-1v0udq-control-plane-7zb4f, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-machine-pool-1v0udq-control-plane-7zb4f, container kube-controller-manager: http2: client connection lost
STEP: Deleting namespace used for hosting the "machine-pool" test spec
INFO: Deleting namespace machine-pool-hb5sz1
STEP: Redacting sensitive information from logs


• [SLOW TEST:1802.574 seconds]
... skipping 56 lines ...
STEP: Dumping logs from the "node-drain-z8iurh" workload cluster
STEP: Dumping workload cluster node-drain-86sii3/node-drain-z8iurh logs
Sep  8 21:51:38.399: INFO: Collecting logs for Linux node node-drain-z8iurh-control-plane-m4bhb in cluster node-drain-z8iurh in namespace node-drain-86sii3

Sep  8 21:58:12.641: INFO: Collecting boot logs for AzureMachine node-drain-z8iurh-control-plane-m4bhb

Failed to get logs for machine node-drain-z8iurh-control-plane-2jfhj, cluster node-drain-86sii3/node-drain-z8iurh: dialing public load balancer at node-drain-z8iurh-69d6a8af.northeurope.cloudapp.azure.com: dial tcp 20.13.194.23:22: connect: connection timed out
STEP: Dumping workload cluster node-drain-86sii3/node-drain-z8iurh kube-system pod logs
STEP: Fetching kube-system pod logs took 1.041550359s
STEP: Dumping workload cluster node-drain-86sii3/node-drain-z8iurh Azure activity log
STEP: Creating log watcher for controller kube-system/etcd-node-drain-z8iurh-control-plane-m4bhb, container etcd
STEP: Collecting events for Pod kube-system/calico-node-kd4fm
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-2xmqd, container calico-kube-controllers
... skipping 34 lines ...
STEP: Tearing down the management cluster



Summarizing 1 Failure:

[Fail] Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck [It] Should successfully trigger KCP remediation 
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.4/framework/controlplane_helpers.go:114

Ran 9 of 23 Specs in 5229.663 seconds
FAIL! -- 8 Passed | 1 Failed | 0 Pending | 14 Skipped


Ginkgo ran 1 suite in 1h28m56.717922882s
Test Suite Failed

Ginkgo 2.0 is coming soon!
==========================
Ginkgo 2.0 is under active development and will introduce several new features, improvements, and a small handful of breaking changes.
A release candidate for 2.0 is now available and 2.0 should GA in Fall 2021.  Please give the RC a try and send us feedback!
  - To learn more, view the migration guide at https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md
  - For instructions on using the Release Candidate visit https://github.com/onsi/ginkgo/blob/ver2/docs/MIGRATING_TO_V2.md#using-the-beta
  - To comment, chime in at https://github.com/onsi/ginkgo/issues/711

To silence this notice, set the environment variable: ACK_GINKGO_RC=true
Alternatively you can: touch $HOME/.ack-ginkgo-rc
make[1]: *** [Makefile:653: test-e2e-run] Error 1
make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make: *** [Makefile:661: test-e2e] Error 2
================ REDACTING LOGS ================
All sensitive variables are redacted
+ EXIT_VALUE=2
+ set +o xtrace
Cleaning up after docker in docker.
================================================================================
... skipping 5 lines ...