This job view page is being replaced by Spyglass soon. Check out the new job view.
Resultfailure
Tests 1 failed / 8 succeeded
Started2022-09-06 20:29
Elapsed1h29m
Revision
uploadercrier
uploadercrier

Test Failures


capz-e2e Running the Cluster API E2E tests Should adopt up-to-date control plane Machines without modification Should adopt up-to-date control plane Machines without modification 26m49s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sRunning\sthe\sCluster\sAPI\sE2E\stests\sShould\sadopt\sup\-to\-date\scontrol\splane\sMachines\swithout\smodification\sShould\sadopt\sup\-to\-date\scontrol\splane\sMachines\swithout\smodification$'
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.4/e2e/kcp_adoption.go:97
Timed out after 1200.001s.
Expected
    <int>: 0
to equal
    <int>: 1
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.4/framework/machines.go:57
				
				Click to see stdout/stderrfrom junit.e2e_suite.3.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 517 lines ...
 ✓ Installing CNI 🔌
 • Installing StorageClass 💾  ...
 ✓ Installing StorageClass 💾
INFO: The kubeconfig file for the kind cluster is /tmp/e2e-kind937999465
INFO: Loading image: "capzci.azurecr.io/cluster-api-azure-controller-amd64:20220906202959"
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-tar2299410939/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-tar3986248646/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-tar4194685133/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-6kcvf, container manager
STEP: Waiting for deployment capi-kubeadm-control-plane-system/capi-kubeadm-control-plane-controller-manager to be available
... skipping 79 lines ...
Sep  6 20:49:07.321: INFO: Collecting boot logs for AzureMachine quick-start-7e12x2-md-0-kbsbf

Sep  6 20:49:07.974: INFO: Collecting logs for Windows node quick-sta-jpxdk in cluster quick-start-7e12x2 in namespace quick-start-46dj6f

Sep  6 20:50:38.328: INFO: Collecting boot logs for AzureMachine quick-start-7e12x2-md-win-jpxdk

Failed to get logs for machine quick-start-7e12x2-md-win-65cf7849dc-2zb57, cluster quick-start-46dj6f/quick-start-7e12x2: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Sep  6 20:50:39.494: INFO: Collecting logs for Windows node quick-sta-s8sx7 in cluster quick-start-7e12x2 in namespace quick-start-46dj6f

Sep  6 20:52:07.298: INFO: Collecting boot logs for AzureMachine quick-start-7e12x2-md-win-s8sx7

Failed to get logs for machine quick-start-7e12x2-md-win-65cf7849dc-xrlvd, cluster quick-start-46dj6f/quick-start-7e12x2: running command "Get-Content "C:\\cni.log"": Process exited with status 1
STEP: Dumping workload cluster quick-start-46dj6f/quick-start-7e12x2 kube-system pod logs
STEP: Collecting events for Pod kube-system/calico-node-6flt4
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-s569q, container calico-kube-controllers
STEP: Creating log watcher for controller kube-system/containerd-logger-bvf8z, container containerd-logger
STEP: Creating log watcher for controller kube-system/calico-node-6flt4, container calico-node
STEP: Fetching kube-system pod logs took 1.154767037s
STEP: Dumping workload cluster quick-start-46dj6f/quick-start-7e12x2 Azure activity log
STEP: Collecting events for Pod kube-system/etcd-quick-start-7e12x2-control-plane-6h8bf
STEP: Creating log watcher for controller kube-system/kube-proxy-d9c7n, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-windows-dzx7b
STEP: failed to find events of Pod "etcd-quick-start-7e12x2-control-plane-6h8bf"
STEP: Collecting events for Pod kube-system/containerd-logger-bvf8z
STEP: Creating log watcher for controller kube-system/containerd-logger-fz6k9, container containerd-logger
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-dzx7b, container kube-proxy
STEP: Collecting events for Pod kube-system/calico-node-wpb8b
STEP: Creating log watcher for controller kube-system/calico-node-windows-h5nnj, container calico-node-startup
STEP: Collecting events for Pod kube-system/kube-scheduler-quick-start-7e12x2-control-plane-6h8bf
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-nr77n, container coredns
STEP: Creating log watcher for controller kube-system/csi-proxy-cvgnt, container csi-proxy
STEP: failed to find events of Pod "kube-scheduler-quick-start-7e12x2-control-plane-6h8bf"
STEP: Collecting events for Pod kube-system/calico-node-windows-h5nnj
STEP: Creating log watcher for controller kube-system/calico-node-windows-xpl5r, container calico-node-startup
STEP: Creating log watcher for controller kube-system/kube-scheduler-quick-start-7e12x2-control-plane-6h8bf, container kube-scheduler
STEP: Creating log watcher for controller kube-system/kube-apiserver-quick-start-7e12x2-control-plane-6h8bf, container kube-apiserver
STEP: Creating log watcher for controller kube-system/calico-node-windows-h5nnj, container calico-node-felix
STEP: Collecting events for Pod kube-system/csi-proxy-cvgnt
STEP: Creating log watcher for controller kube-system/csi-proxy-rblkh, container csi-proxy
STEP: Creating log watcher for controller kube-system/calico-node-windows-xpl5r, container calico-node-felix
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-nr77n
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-tgr7b, container coredns
STEP: Collecting events for Pod kube-system/kube-apiserver-quick-start-7e12x2-control-plane-6h8bf
STEP: failed to find events of Pod "kube-apiserver-quick-start-7e12x2-control-plane-6h8bf"
STEP: Creating log watcher for controller kube-system/kube-controller-manager-quick-start-7e12x2-control-plane-6h8bf, container kube-controller-manager
STEP: Collecting events for Pod kube-system/csi-proxy-rblkh
STEP: Creating log watcher for controller kube-system/kube-proxy-9mz9h, container kube-proxy
STEP: Creating log watcher for controller kube-system/etcd-quick-start-7e12x2-control-plane-6h8bf, container etcd
STEP: Collecting events for Pod kube-system/calico-node-windows-xpl5r
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-s569q
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-tgr7b
STEP: Collecting events for Pod kube-system/containerd-logger-fz6k9
STEP: Creating log watcher for controller kube-system/calico-node-wpb8b, container calico-node
STEP: Collecting events for Pod kube-system/kube-proxy-9mz9h
STEP: Collecting events for Pod kube-system/kube-controller-manager-quick-start-7e12x2-control-plane-6h8bf
STEP: Collecting events for Pod kube-system/kube-proxy-d9c7n
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-4kzjz, container kube-proxy
STEP: failed to find events of Pod "kube-controller-manager-quick-start-7e12x2-control-plane-6h8bf"
STEP: Collecting events for Pod kube-system/kube-proxy-windows-4kzjz
STEP: Fetching activity logs took 2.137935042s
STEP: Dumping all the Cluster API resources in the "quick-start-46dj6f" namespace
STEP: Deleting cluster quick-start-46dj6f/quick-start-7e12x2
STEP: Deleting cluster quick-start-7e12x2
INFO: Waiting for the Cluster quick-start-46dj6f/quick-start-7e12x2 to be deleted
STEP: Waiting for cluster quick-start-7e12x2 to be deleted
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-s569q, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-tgr7b, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-xpl5r, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-6flt4, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-xpl5r, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-d9c7n, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-fz6k9, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-wpb8b, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-9mz9h, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-quick-start-7e12x2-control-plane-6h8bf, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-quick-start-7e12x2-control-plane-6h8bf, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-h5nnj, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-4kzjz, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-quick-start-7e12x2-control-plane-6h8bf, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-dzx7b, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-quick-start-7e12x2-control-plane-6h8bf, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-rblkh, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-h5nnj, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-nr77n, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-cvgnt, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/containerd-logger-bvf8z, container containerd-logger: http2: client connection lost
STEP: Deleting namespace used for hosting the "quick-start" test spec
INFO: Deleting namespace quick-start-46dj6f
STEP: Redacting sensitive information from logs


• [SLOW TEST:1090.482 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  6 20:40:06.428: INFO: starting to create namespace for hosting the "self-hosted" test spec
2022/09/06 20:40:06 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-agvusq" 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-agvusq --infrastructure (default) --kubernetes-version v1.22.13 --control-plane-machine-count 1 --worker-machine-count 1 --flavor management
... skipping 60 lines ...
STEP: Fetching kube-system pod logs took 700.454938ms
STEP: Dumping workload cluster self-hosted/self-hosted-agvusq Azure activity log
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-kflv7, container calico-kube-controllers
STEP: Collecting events for Pod kube-system/etcd-self-hosted-agvusq-control-plane-w7rjw
STEP: Creating log watcher for controller kube-system/kube-controller-manager-self-hosted-agvusq-control-plane-w7rjw, container kube-controller-manager
STEP: Collecting events for Pod kube-system/kube-controller-manager-self-hosted-agvusq-control-plane-w7rjw
STEP: failed to find events of Pod "etcd-self-hosted-agvusq-control-plane-w7rjw"
STEP: failed to find events of Pod "kube-controller-manager-self-hosted-agvusq-control-plane-w7rjw"
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-kflv7
STEP: Collecting events for Pod kube-system/kube-proxy-t48jn
STEP: Creating log watcher for controller kube-system/calico-node-c6r6x, container calico-node
STEP: Creating log watcher for controller kube-system/kube-apiserver-self-hosted-agvusq-control-plane-w7rjw, container kube-apiserver
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-hzch8, container coredns
STEP: Creating log watcher for controller kube-system/kube-scheduler-self-hosted-agvusq-control-plane-w7rjw, container kube-scheduler
STEP: Collecting events for Pod kube-system/kube-scheduler-self-hosted-agvusq-control-plane-w7rjw
STEP: failed to find events of Pod "kube-scheduler-self-hosted-agvusq-control-plane-w7rjw"
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-xk87t, container coredns
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-xk87t
STEP: Creating log watcher for controller kube-system/kube-proxy-t48jn, container kube-proxy
STEP: Creating log watcher for controller kube-system/etcd-self-hosted-agvusq-control-plane-w7rjw, container etcd
STEP: Collecting events for Pod kube-system/kube-apiserver-self-hosted-agvusq-control-plane-w7rjw
STEP: failed to find events of Pod "kube-apiserver-self-hosted-agvusq-control-plane-w7rjw"
STEP: Creating log watcher for controller kube-system/calico-node-wn8v4, container calico-node
STEP: Collecting events for Pod kube-system/calico-node-wn8v4
STEP: Collecting events for Pod kube-system/calico-node-c6r6x
STEP: Creating log watcher for controller kube-system/kube-proxy-tjm69, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-tjm69
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-hzch8
... skipping 84 lines ...
Sep  6 20:55:28.678: INFO: Collecting boot logs for AzureMachine md-rollout-h7dsvh-md-0-w37zau-g9pwr

Sep  6 20:55:29.222: INFO: Collecting logs for Windows node md-rollou-9x88b in cluster md-rollout-h7dsvh in namespace md-rollout-7l9if7

Sep  6 20:56:56.121: INFO: Collecting boot logs for AzureMachine md-rollout-h7dsvh-md-win-9whmg7-9x88b

Failed to get logs for machine md-rollout-h7dsvh-md-win-5cb7bf86df-kzlb5, cluster md-rollout-7l9if7/md-rollout-h7dsvh: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Sep  6 20:56:56.526: INFO: Collecting logs for Windows node md-rollou-m8x89 in cluster md-rollout-h7dsvh in namespace md-rollout-7l9if7

Sep  6 20:58:27.229: INFO: Collecting boot logs for AzureMachine md-rollout-h7dsvh-md-win-m8x89

Failed to get logs for machine md-rollout-h7dsvh-md-win-5cfff79bbf-7q4wx, cluster md-rollout-7l9if7/md-rollout-h7dsvh: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Failed to get logs for machine md-rollout-h7dsvh-md-win-5cfff79bbf-cxmbd, cluster md-rollout-7l9if7/md-rollout-h7dsvh: azuremachines.infrastructure.cluster.x-k8s.io "md-rollout-h7dsvh-md-win-b8tph" not found
STEP: Dumping workload cluster md-rollout-7l9if7/md-rollout-h7dsvh kube-system pod logs
STEP: Creating log watcher for controller kube-system/calico-node-windows-smbx4, container calico-node-startup
STEP: Collecting events for Pod kube-system/kube-scheduler-md-rollout-h7dsvh-control-plane-6mshx
STEP: Creating log watcher for controller kube-system/calico-node-tzvvr, container calico-node
STEP: failed to find events of Pod "kube-scheduler-md-rollout-h7dsvh-control-plane-6mshx"
STEP: Creating log watcher for controller kube-system/calico-node-windows-smbx4, container calico-node-felix
STEP: Collecting events for Pod kube-system/calico-node-tzvvr
STEP: Creating log watcher for controller kube-system/calico-node-windows-84gm4, container calico-node-startup
STEP: Collecting events for Pod kube-system/calico-node-windows-smbx4
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-g5cmt, container calico-kube-controllers
STEP: Creating log watcher for controller kube-system/calico-node-windows-zhsbj, container calico-node-startup
... skipping 3 lines ...
STEP: Creating log watcher for controller kube-system/calico-node-sjdbc, container calico-node
STEP: Fetching kube-system pod logs took 1.181005049s
STEP: Dumping workload cluster md-rollout-7l9if7/md-rollout-h7dsvh Azure activity log
STEP: Collecting events for Pod kube-system/calico-node-sjdbc
STEP: Collecting events for Pod kube-system/etcd-md-rollout-h7dsvh-control-plane-6mshx
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-g5cmt
STEP: failed to find events of Pod "etcd-md-rollout-h7dsvh-control-plane-6mshx"
STEP: Collecting events for Pod kube-system/kube-proxy-njmzg
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-5n7xd, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-apiserver-md-rollout-h7dsvh-control-plane-6mshx, container kube-apiserver
STEP: Creating log watcher for controller kube-system/calico-node-windows-zhsbj, container calico-node-felix
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-6jncn, container coredns
STEP: Collecting events for Pod kube-system/kube-controller-manager-md-rollout-h7dsvh-control-plane-6mshx
STEP: failed to find events of Pod "kube-controller-manager-md-rollout-h7dsvh-control-plane-6mshx"
STEP: Collecting events for Pod kube-system/kube-apiserver-md-rollout-h7dsvh-control-plane-6mshx
STEP: failed to find events of Pod "kube-apiserver-md-rollout-h7dsvh-control-plane-6mshx"
STEP: Creating log watcher for controller kube-system/kube-controller-manager-md-rollout-h7dsvh-control-plane-6mshx, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/containerd-logger-m7gfh, container containerd-logger
STEP: Creating log watcher for controller kube-system/kube-proxy-jl8dn, container kube-proxy
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-7zr8k, container coredns
STEP: Collecting events for Pod kube-system/kube-proxy-windows-5n7xd
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-dxskg, container kube-proxy
... skipping 12 lines ...
STEP: Creating log watcher for controller kube-system/kube-scheduler-md-rollout-h7dsvh-control-plane-6mshx, container kube-scheduler
STEP: Collecting events for Pod kube-system/csi-proxy-kbzkk
STEP: Collecting events for Pod kube-system/kube-proxy-windows-dxskg
STEP: Collecting events for Pod kube-system/csi-proxy-2f8s4
STEP: Collecting events for Pod kube-system/containerd-logger-54llm
STEP: Creating log watcher for controller kube-system/csi-proxy-2f8s4, container csi-proxy
STEP: Error starting logs stream for pod kube-system/kube-proxy-windows-5n7xd, container kube-proxy: container "kube-proxy" in pod "kube-proxy-windows-5n7xd" is waiting to start: ContainerCreating
STEP: Error starting logs stream for pod kube-system/calico-node-windows-zhsbj, container calico-node-felix: container "calico-node-felix" in pod "calico-node-windows-zhsbj" is waiting to start: PodInitializing
STEP: Error starting logs stream for pod kube-system/calico-node-windows-zhsbj, container calico-node-startup: container "calico-node-startup" in pod "calico-node-windows-zhsbj" is waiting to start: PodInitializing
STEP: Error starting logs stream for pod kube-system/containerd-logger-m7gfh, container containerd-logger: container "containerd-logger" in pod "containerd-logger-m7gfh" is waiting to start: ContainerCreating
STEP: Fetching activity logs took 2.297817919s
STEP: Dumping all the Cluster API resources in the "md-rollout-7l9if7" namespace
STEP: Deleting cluster md-rollout-7l9if7/md-rollout-h7dsvh
STEP: Deleting cluster md-rollout-h7dsvh
INFO: Waiting for the Cluster md-rollout-7l9if7/md-rollout-h7dsvh to be deleted
STEP: Waiting for cluster md-rollout-h7dsvh to be deleted
STEP: Got error while streaming logs for pod kube-system/containerd-logger-s6pc4, container containerd-logger: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-md-rollout-h7dsvh-control-plane-6mshx, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-g5cmt, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-windows-dxskg, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-md-rollout-h7dsvh-control-plane-6mshx, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-njmzg, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-md-rollout-h7dsvh-control-plane-6mshx, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-md-rollout-h7dsvh-control-plane-6mshx, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-sjdbc, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-84gm4, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-84gm4, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-6jncn, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/csi-proxy-2f8s4, container csi-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-7zr8k, container coredns: http2: client connection lost
STEP: Deleting namespace used for hosting the "md-rollout" test spec
INFO: Deleting namespace md-rollout-7l9if7
STEP: Redacting sensitive information from logs


• [SLOW TEST:1572.841 seconds]
... skipping 62 lines ...
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-kb2zr
STEP: Collecting events for Pod kube-system/kube-controller-manager-mhc-remediation-w5ep9h-control-plane-hr4b2
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-fm9dg
STEP: Collecting events for Pod kube-system/kube-proxy-xvwnx
STEP: Collecting events for Pod kube-system/etcd-mhc-remediation-w5ep9h-control-plane-hr4b2
STEP: Creating log watcher for controller kube-system/kube-apiserver-mhc-remediation-w5ep9h-control-plane-hr4b2, container kube-apiserver
STEP: failed to find events of Pod "kube-controller-manager-mhc-remediation-w5ep9h-control-plane-hr4b2"
STEP: Collecting events for Pod kube-system/kube-scheduler-mhc-remediation-w5ep9h-control-plane-hr4b2
STEP: Creating log watcher for controller kube-system/etcd-mhc-remediation-w5ep9h-control-plane-hr4b2, container etcd
STEP: Dumping workload cluster mhc-remediation-jmz1v7/mhc-remediation-w5ep9h Azure activity log
STEP: Creating log watcher for controller kube-system/calico-node-vk4gh, container calico-node
STEP: Collecting events for Pod kube-system/calico-node-vk4gh
STEP: failed to find events of Pod "etcd-mhc-remediation-w5ep9h-control-plane-hr4b2"
STEP: Creating log watcher for controller kube-system/calico-node-2w5gp, container calico-node
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-kb2zr, container coredns
STEP: failed to find events of Pod "kube-scheduler-mhc-remediation-w5ep9h-control-plane-hr4b2"
STEP: Creating log watcher for controller kube-system/kube-controller-manager-mhc-remediation-w5ep9h-control-plane-hr4b2, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-969cf87c4-fm9dg, container calico-kube-controllers
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-kgdz7, container coredns
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-kgdz7
STEP: Creating log watcher for controller kube-system/kube-proxy-xvwnx, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-54px6, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-54px6
STEP: Creating log watcher for controller kube-system/kube-scheduler-mhc-remediation-w5ep9h-control-plane-hr4b2, container kube-scheduler
STEP: Collecting events for Pod kube-system/calico-node-2w5gp
STEP: Collecting events for Pod kube-system/kube-apiserver-mhc-remediation-w5ep9h-control-plane-hr4b2
STEP: failed to find events of Pod "kube-apiserver-mhc-remediation-w5ep9h-control-plane-hr4b2"
STEP: Fetching activity logs took 1.676841362s
STEP: Dumping all the Cluster API resources in the "mhc-remediation-jmz1v7" namespace
STEP: Deleting cluster mhc-remediation-jmz1v7/mhc-remediation-w5ep9h
STEP: Deleting cluster mhc-remediation-w5ep9h
INFO: Waiting for the Cluster mhc-remediation-jmz1v7/mhc-remediation-w5ep9h to be deleted
STEP: Waiting for cluster mhc-remediation-w5ep9h to be deleted
... skipping 172 lines ...
STEP: Fetching kube-system pod logs took 33.984047389s
STEP: Dumping workload cluster kcp-adoption-xlhkju/kcp-adoption-n8lt3k Azure activity log
STEP: Creating log watcher for controller kube-system/etcd-kcp-adoption-n8lt3k-control-plane-0, container etcd
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-bk7gc
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-bk7gc, container coredns
STEP: Collecting events for Pod kube-system/kube-controller-manager-kcp-adoption-n8lt3k-control-plane-0
STEP: failed to find events of Pod "kube-controller-manager-kcp-adoption-n8lt3k-control-plane-0"
STEP: Creating log watcher for controller kube-system/kube-proxy-b6cjp, container kube-proxy
STEP: Collecting events for Pod kube-system/coredns-78fcd69978-kgbwn
STEP: Collecting events for Pod kube-system/etcd-kcp-adoption-n8lt3k-control-plane-0
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-kgbwn, container coredns
STEP: Creating log watcher for controller kube-system/kube-apiserver-kcp-adoption-n8lt3k-control-plane-0, container kube-apiserver
STEP: failed to find events of Pod "etcd-kcp-adoption-n8lt3k-control-plane-0"
STEP: Collecting events for Pod kube-system/kube-apiserver-kcp-adoption-n8lt3k-control-plane-0
STEP: failed to find events of Pod "kube-apiserver-kcp-adoption-n8lt3k-control-plane-0"
STEP: Collecting events for Pod kube-system/kube-scheduler-kcp-adoption-n8lt3k-control-plane-0
STEP: failed to find events of Pod "kube-scheduler-kcp-adoption-n8lt3k-control-plane-0"
STEP: Collecting events for Pod kube-system/kube-proxy-b6cjp
STEP: Creating log watcher for controller kube-system/kube-scheduler-kcp-adoption-n8lt3k-control-plane-0, container kube-scheduler
STEP: Creating log watcher for controller kube-system/kube-controller-manager-kcp-adoption-n8lt3k-control-plane-0, container kube-controller-manager
STEP: Fetching activity logs took 1.115751128s
STEP: Dumping all the Cluster API resources in the "kcp-adoption-xlhkju" namespace
STEP: Deleting cluster kcp-adoption-xlhkju/kcp-adoption-n8lt3k
... skipping 151 lines ...
STEP: Fetching activity logs took 1.242965551s
STEP: Dumping all the Cluster API resources in the "machine-pool-zoscva" namespace
STEP: Deleting cluster machine-pool-zoscva/machine-pool-cryg64
STEP: Deleting cluster machine-pool-cryg64
INFO: Waiting for the Cluster machine-pool-zoscva/machine-pool-cryg64 to be deleted
STEP: Waiting for cluster machine-pool-cryg64 to be deleted
STEP: Error starting logs stream for pod kube-system/kube-proxy-rc9zd, container kube-proxy: Get "https://10.1.0.4:10250/containerLogs/kube-system/kube-proxy-rc9zd/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-jszcb, container kube-proxy: Get "https://10.1.0.8:10250/containerLogs/kube-system/kube-proxy-jszcb/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-ggp9d, container calico-node: Get "https://10.1.0.8:10250/containerLogs/kube-system/calico-node-ggp9d/calico-node?follow=true": dial tcp 10.1.0.8:10250: i/o timeout
STEP: Error starting logs stream for pod kube-system/calico-node-45ztt, container calico-node: Get "https://10.1.0.4:10250/containerLogs/kube-system/calico-node-45ztt/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-4tmfq, container calico-node: Get "https://10.1.0.5:10250/containerLogs/kube-system/calico-node-4tmfq/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-ntj24, container kube-proxy: Get "https://10.1.0.5:10250/containerLogs/kube-system/kube-proxy-ntj24/kube-proxy?follow=true": dial tcp 10.1.0.5:10250: i/o timeout
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-machine-pool-cryg64-control-plane-p8jqw, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-2kddr, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-969cf87c4-7ch52, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-machine-pool-cryg64-control-plane-p8jqw, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-machine-pool-cryg64-control-plane-p8jqw, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-xndz2, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-655hm, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-machine-pool-cryg64-control-plane-p8jqw, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-rw7rd, container coredns: http2: client connection lost
STEP: Deleting namespace used for hosting the "machine-pool" test spec
INFO: Deleting namespace machine-pool-zoscva
STEP: Redacting sensitive information from logs


• [SLOW TEST:1660.530 seconds]
... skipping 67 lines ...
Sep  6 21:36:01.205: INFO: Collecting boot logs for AzureMachine md-scale-guzlic-md-0-z7whm

Sep  6 21:36:01.733: INFO: Collecting logs for Windows node md-scale-cb57j in cluster md-scale-guzlic in namespace md-scale-7jnd0a

Sep  6 21:41:04.757: INFO: Collecting boot logs for AzureMachine md-scale-guzlic-md-win-cb57j

Failed to get logs for machine md-scale-guzlic-md-win-85b6dc95c8-p85np, cluster md-scale-7jnd0a/md-scale-guzlic: running command "Get-Content "C:\\cni.log"": Process exited with status 1
Sep  6 21:41:05.881: INFO: Collecting logs for Windows node md-scale-x8cqp in cluster md-scale-guzlic in namespace md-scale-7jnd0a

Sep  6 21:44:45.016: INFO: Collecting boot logs for AzureMachine md-scale-guzlic-md-win-x8cqp

Failed to get logs for machine md-scale-guzlic-md-win-85b6dc95c8-z4wgc, cluster md-scale-7jnd0a/md-scale-guzlic: running command "Get-Content "C:\\cni.log"": Process exited with status 1
STEP: Dumping workload cluster md-scale-7jnd0a/md-scale-guzlic kube-system pod logs
STEP: Fetching kube-system pod logs took 2.375586457s
STEP: Dumping workload cluster md-scale-7jnd0a/md-scale-guzlic Azure activity log
STEP: Creating log watcher for controller kube-system/calico-node-5wffb, container calico-node
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-q7h5x, container kube-proxy
STEP: Collecting events for Pod kube-system/kube-proxy-l8dbl
... skipping 138 lines ...
STEP: Creating log watcher for controller kube-system/kube-apiserver-node-drain-q69l0s-control-plane-ddvsh, container kube-apiserver
STEP: Collecting events for Pod kube-system/kube-controller-manager-node-drain-q69l0s-control-plane-ddvsh
STEP: Creating log watcher for controller kube-system/kube-controller-manager-node-drain-q69l0s-control-plane-ddvsh, container kube-controller-manager
STEP: Collecting events for Pod kube-system/calico-kube-controllers-969cf87c4-bjwp4
STEP: Collecting events for Pod kube-system/kube-apiserver-node-drain-q69l0s-control-plane-ddvsh
STEP: Collecting events for Pod kube-system/etcd-node-drain-q69l0s-control-plane-ddvsh
STEP: Error starting logs stream for pod kube-system/calico-node-lpqhv, container calico-node: pods "node-drain-q69l0s-control-plane-ddvsh" not found
STEP: Error starting logs stream for pod kube-system/kube-scheduler-node-drain-q69l0s-control-plane-ddvsh, container kube-scheduler: pods "node-drain-q69l0s-control-plane-ddvsh" not found
STEP: Error starting logs stream for pod kube-system/etcd-node-drain-q69l0s-control-plane-ddvsh, container etcd: pods "node-drain-q69l0s-control-plane-ddvsh" not found
STEP: Error starting logs stream for pod kube-system/kube-proxy-pwv4x, container kube-proxy: pods "node-drain-q69l0s-control-plane-ddvsh" not found
STEP: Error starting logs stream for pod kube-system/kube-controller-manager-node-drain-q69l0s-control-plane-ddvsh, container kube-controller-manager: pods "node-drain-q69l0s-control-plane-ddvsh" not found
STEP: Error starting logs stream for pod kube-system/kube-apiserver-node-drain-q69l0s-control-plane-ddvsh, container kube-apiserver: pods "node-drain-q69l0s-control-plane-ddvsh" not found
STEP: Fetching activity logs took 2.734937512s
STEP: Dumping all the Cluster API resources in the "node-drain-9i6z1r" namespace
STEP: Deleting cluster node-drain-9i6z1r/node-drain-q69l0s
STEP: Deleting cluster node-drain-q69l0s
INFO: Waiting for the Cluster node-drain-9i6z1r/node-drain-q69l0s to be deleted
STEP: Waiting for cluster node-drain-q69l0s to be deleted
... skipping 13 lines ...
STEP: Tearing down the management cluster



Summarizing 1 Failure:

[Fail] Running the Cluster API E2E tests Should adopt up-to-date control plane Machines without modification [It] Should adopt up-to-date control plane Machines without modification 
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.1.4/framework/machines.go:57

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


Ginkgo ran 1 suite in 1h23m9.359197403s
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 ...