This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 1 failed / 5 succeeded
Started2021-11-19 18:35
Elapsed2h15m
Revisionmain

Test Failures


capz-e2e Workload cluster creation Creating a GPU-enabled cluster with a single control plane node and 1 node 35m30s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\sWorkload\scluster\screation\sCreating\sa\sGPU\-enabled\scluster\swith\sa\ssingle\scontrol\splane\snode\sand\s1\snode$'
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:413
Timed out after 1200.000s.
Expected
    <bool>: false
to be true
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_gpu.go:76
				
				Click to see stdout/stderrfrom junit.e2e_suite.3.xml

Filter through log files | View test history on testgrid


Show 5 Passed Tests

Show 15 Skipped Tests

Error lines from build-log.txt

... skipping 432 lines ...
  With ipv6 worker node
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:288

INFO: "With ipv6 worker node" started at Fri, 19 Nov 2021 18:45:18 UTC on Ginkgo node 3 of 3
STEP: Creating namespace "capz-e2e-zj0hkz" for hosting the cluster
Nov 19 18:45:18.682: INFO: starting to create namespace for hosting the "capz-e2e-zj0hkz" test spec
2021/11/19 18:45:18 failed trying to get namespace (capz-e2e-zj0hkz):namespaces "capz-e2e-zj0hkz" not found
INFO: Creating namespace capz-e2e-zj0hkz
INFO: Creating event watcher for namespace "capz-e2e-zj0hkz"
Nov 19 18:45:18.735: INFO: Creating cluster identity secret
%!(EXTRA string=cluster-identity-secret)INFO: Cluster name is capz-e2e-zj0hkz-ipv6
INFO: Creating the workload cluster with name "capz-e2e-zj0hkz-ipv6" using the "ipv6" template (Kubernetes v1.22.4, 3 control-plane machines, 1 worker machines)
INFO: Getting the cluster template yaml
... skipping 115 lines ...
  with a single control plane node and an AzureMachinePool with 2 Linux and 2 Windows worker nodes
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:334

INFO: "with a single control plane node and an AzureMachinePool with 2 Linux and 2 Windows worker nodes" started at Fri, 19 Nov 2021 19:03:24 UTC on Ginkgo node 3 of 3
STEP: Creating namespace "capz-e2e-dz4h5b" for hosting the cluster
Nov 19 19:03:24.131: INFO: starting to create namespace for hosting the "capz-e2e-dz4h5b" test spec
2021/11/19 19:03:24 failed trying to get namespace (capz-e2e-dz4h5b):namespaces "capz-e2e-dz4h5b" not found
INFO: Creating namespace capz-e2e-dz4h5b
INFO: Creating event watcher for namespace "capz-e2e-dz4h5b"
Nov 19 19:03:24.167: INFO: Creating cluster identity secret
%!(EXTRA string=cluster-identity-secret)INFO: Cluster name is capz-e2e-dz4h5b-vmss
INFO: Creating the workload cluster with name "capz-e2e-dz4h5b-vmss" using the "machine-pool" template (Kubernetes v1.22.4, 1 control-plane machines, 2 worker machines)
INFO: Getting the cluster template yaml
... skipping 142 lines ...
Nov 19 19:23:18.802: INFO: INFO: Collecting boot logs for VMSS instance 0 of scale set capz-e2e-dz4h5b-vmss-mp-0

Nov 19 19:23:19.321: INFO: INFO: Collecting logs for node win-p-win000001 in cluster capz-e2e-dz4h5b-vmss in namespace capz-e2e-dz4h5b

Nov 19 19:23:36.242: INFO: INFO: Collecting boot logs for VMSS instance 1 of scale set capz-e2e-dz4h5b-vmss-mp-0

Failed to get logs for machine pool capz-e2e-dz4h5b-vmss-mp-0, cluster capz-e2e-dz4h5b/capz-e2e-dz4h5b-vmss: [[running command "cat /var/log/cloud-init.log": Process exited with status 1, running command "cat /var/log/cloud-init-output.log": Process exited with status 1, running command "journalctl --no-pager --output=short-precise -u kubelet.service": Process exited with status 1, running command "journalctl --no-pager --output=short-precise -u containerd.service": Process exited with status 1, running command "journalctl --no-pager --output=short-precise": Process exited with status 1, running command "journalctl --no-pager --output=short-precise -k": Process exited with status 1], [running command "cat /var/log/cloud-init-output.log": Process exited with status 1, running command "cat /var/log/cloud-init.log": Process exited with status 1, running command "journalctl --no-pager --output=short-precise -k": Process exited with status 1, running command "journalctl --no-pager --output=short-precise": Process exited with status 1, running command "journalctl --no-pager --output=short-precise -u containerd.service": Process exited with status 1, running command "journalctl --no-pager --output=short-precise -u kubelet.service": Process exited with status 1]]
Nov 19 19:23:36.707: INFO: INFO: Collecting logs for node win-p-win000000 in cluster capz-e2e-dz4h5b-vmss in namespace capz-e2e-dz4h5b

Nov 19 19:24:01.656: INFO: INFO: Collecting boot logs for VMSS instance 0 of scale set win-p-win

Nov 19 19:24:02.071: INFO: INFO: Collecting logs for node win-p-win000001 in cluster capz-e2e-dz4h5b-vmss in namespace capz-e2e-dz4h5b

Nov 19 19:24:32.215: INFO: INFO: Collecting boot logs for VMSS instance 1 of scale set win-p-win

Failed to get logs for machine pool capz-e2e-dz4h5b-vmss-mp-win, cluster capz-e2e-dz4h5b/capz-e2e-dz4h5b-vmss: [running command "get-eventlog -LogName Application -Source Docker | Select-Object Index, TimeGenerated, EntryType, Message | Sort-Object Index | Format-Table -Wrap -Autosize": Process exited with status 1, running command "docker ps -a": Process exited with status 1]
STEP: Dumping workload cluster capz-e2e-dz4h5b/capz-e2e-dz4h5b-vmss kube-system pod logs
STEP: Creating log watcher for controller kube-system/calico-node-windows-bs6hz, container calico-node-felix
STEP: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-dz4h5b-vmss-control-plane-75zfg, container kube-apiserver
STEP: Creating log watcher for controller kube-system/kube-proxy-db59w, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-controller-manager-capz-e2e-dz4h5b-vmss-control-plane-75zfg, container kube-controller-manager
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-846b5f484d-d9z8t, container calico-kube-controllers
... skipping 10 lines ...
STEP: Creating log watcher for controller kube-system/calico-node-gkvp7, container calico-node
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-8mlj5, container coredns
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-9kgw4, container coredns
STEP: Creating log watcher for controller kube-system/etcd-capz-e2e-dz4h5b-vmss-control-plane-75zfg, container etcd
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-t69dh, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-jq84b, container kube-proxy
STEP: Error starting logs stream for pod kube-system/kube-proxy-windows-t69dh, container kube-proxy: container "kube-proxy" in pod "kube-proxy-windows-t69dh" is waiting to start: trying and failing to pull image
STEP: Error starting logs stream for pod kube-system/kube-proxy-windows-jq84b, container kube-proxy: container "kube-proxy" in pod "kube-proxy-windows-jq84b" is waiting to start: trying and failing to pull image
STEP: Got error while iterating over activity logs for resource group capz-e2e-dz4h5b-vmss: insights.ActivityLogsClient#listNextResults: Failure sending next results request: StatusCode=500 -- Original Error: context deadline exceeded
STEP: Fetching activity logs took 30.001008997s
STEP: Dumping all the Cluster API resources in the "capz-e2e-dz4h5b" namespace
STEP: Deleting all clusters in the capz-e2e-dz4h5b namespace
STEP: Deleting cluster capz-e2e-dz4h5b-vmss
INFO: Waiting for the Cluster capz-e2e-dz4h5b/capz-e2e-dz4h5b-vmss to be deleted
STEP: Waiting for cluster capz-e2e-dz4h5b-vmss to be deleted
STEP: Got error while streaming logs for pod kube-system/kube-scheduler-capz-e2e-dz4h5b-vmss-control-plane-75zfg, container kube-scheduler: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-bs6hz, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-p7jbb, container calico-node-startup: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-8mlj5, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/coredns-78fcd69978-9kgw4, container coredns: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-apiserver-capz-e2e-dz4h5b-vmss-control-plane-75zfg, container kube-apiserver: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-bz5z5, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/etcd-capz-e2e-dz4h5b-vmss-control-plane-75zfg, container etcd: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-kube-controllers-846b5f484d-d9z8t, container calico-kube-controllers: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-p7jbb, container calico-node-felix: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-gkvp7, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-controller-manager-capz-e2e-dz4h5b-vmss-control-plane-75zfg, container kube-controller-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-jsgq9, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-db59w, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-windows-bs6hz, container calico-node-felix: http2: client connection lost
STEP: Deleting namespace used for hosting the "create-workload-cluster" test spec
INFO: Deleting namespace capz-e2e-dz4h5b
STEP: Checking if any resources are left over in Azure for spec "create-workload-cluster"
STEP: Redacting sensitive information from logs
INFO: "with a single control plane node and an AzureMachinePool with 2 Linux and 2 Windows worker nodes" ran for 29m57s on Ginkgo node 3 of 3

... skipping 10 lines ...
  With 3 control-plane nodes and 2 Linux and 2 Windows worker nodes
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:205

INFO: "With 3 control-plane nodes and 2 Linux and 2 Windows worker nodes" started at Fri, 19 Nov 2021 18:45:12 UTC on Ginkgo node 1 of 3
STEP: Creating namespace "capz-e2e-7afkwh" for hosting the cluster
Nov 19 18:45:12.606: INFO: starting to create namespace for hosting the "capz-e2e-7afkwh" test spec
2021/11/19 18:45:12 failed trying to get namespace (capz-e2e-7afkwh):namespaces "capz-e2e-7afkwh" not found
INFO: Creating namespace capz-e2e-7afkwh
INFO: Creating event watcher for namespace "capz-e2e-7afkwh"
Nov 19 18:45:12.636: INFO: Creating cluster identity secret
%!(EXTRA string=cluster-identity-secret)INFO: Cluster name is capz-e2e-7afkwh-ha
INFO: Creating the workload cluster with name "capz-e2e-7afkwh-ha" using the "(default)" template (Kubernetes v1.22.4, 3 control-plane machines, 2 worker machines)
INFO: Getting the cluster template yaml
... skipping 75 lines ...
Nov 19 18:57:23.462: INFO: starting to delete external LB service web3w6u74-elb
Nov 19 18:57:23.636: INFO: starting to delete deployment web3w6u74
Nov 19 18:57:23.752: INFO: starting to delete job curl-to-elb-jobebu317vzy3w
STEP: creating a Kubernetes client to the workload cluster
STEP: Creating development namespace
Nov 19 18:57:23.909: INFO: starting to create dev deployment namespace
2021/11/19 18:57:24 failed trying to get namespace (development):namespaces "development" not found
2021/11/19 18:57:24 namespace development does not exist, creating...
STEP: Creating production namespace
Nov 19 18:57:24.142: INFO: starting to create prod deployment namespace
2021/11/19 18:57:24 failed trying to get namespace (production):namespaces "production" not found
2021/11/19 18:57:24 namespace production does not exist, creating...
STEP: Creating frontendProd, backend and network-policy pod deployments
Nov 19 18:57:24.377: INFO: starting to create frontend-prod deployments
Nov 19 18:57:24.492: INFO: starting to create frontend-dev deployments
Nov 19 18:57:24.607: INFO: starting to create backend deployments
Nov 19 18:57:24.721: INFO: starting to create network-policy deployments
... skipping 11 lines ...
STEP: Ensuring we have outbound internet access from the network-policy pods
STEP: Ensuring we have connectivity from network-policy pods to frontend-prod pods
STEP: Ensuring we have connectivity from network-policy pods to backend pods
STEP: Applying a network policy to deny ingress access to app: webapp, role: backend pods in development namespace
Nov 19 18:57:52.024: INFO: starting to applying a network policy development/backend-deny-ingress to deny access to app: webapp, role: backend pods in development namespace
STEP: Ensuring we no longer have ingress access from the network-policy pods to backend pods
curl: (7) Failed to connect to 192.168.214.67 port 80: Connection timed out

STEP: Cleaning up after ourselves
Nov 19 19:00:03.533: INFO: starting to cleaning up network policy development/backend-deny-ingress after ourselves
STEP: Applying a network policy to deny egress access in development namespace
Nov 19 19:00:03.953: INFO: starting to applying a network policy development/backend-deny-egress to deny egress access in development namespace
STEP: Ensuring we no longer have egress access from the network-policy pods to backend pods
curl: (7) Failed to connect to 192.168.214.67 port 80: Connection timed out

curl: (7) Failed to connect to 192.168.214.67 port 80: Connection timed out

STEP: Cleaning up after ourselves
Nov 19 19:04:25.937: INFO: starting to cleaning up network policy development/backend-deny-egress after ourselves
STEP: Applying a network policy to allow egress access to app: webapp, role: frontend pods in any namespace from pods with app: webapp, role: backend labels in development namespace
Nov 19 19:04:26.351: INFO: starting to applying a network policy development/backend-allow-egress-pod-label to allow egress access to app: webapp, role: frontend pods in any namespace from pods with app: webapp, role: backend labels in development namespace
STEP: Ensuring we have egress access from pods with matching labels
STEP: Ensuring we don't have ingress access from pods without matching labels
curl: (7) Failed to connect to 192.168.138.4 port 80: Connection timed out

STEP: Cleaning up after ourselves
Nov 19 19:06:39.059: INFO: starting to cleaning up network policy development/backend-allow-egress-pod-label after ourselves
STEP: Applying a network policy to allow egress access to app: webapp, role: frontend pods from pods with app: webapp, role: backend labels in same development namespace
Nov 19 19:06:39.457: INFO: starting to applying a network policy development/backend-allow-egress-pod-namespace-label to allow egress access to app: webapp, role: frontend pods from pods with app: webapp, role: backend labels in same development namespace
STEP: Ensuring we have egress access from pods with matching labels
STEP: Ensuring we don't have ingress access from pods without matching labels
curl: (7) Failed to connect to 192.168.138.3 port 80: Connection timed out

curl: (7) Failed to connect to 192.168.138.4 port 80: Connection timed out

STEP: Cleaning up after ourselves
Nov 19 19:11:03.251: INFO: starting to cleaning up network policy development/backend-allow-egress-pod-namespace-label after ourselves
STEP: Applying a network policy to only allow ingress access to app: webapp, role: backend pods in development namespace from pods in any namespace with the same labels
Nov 19 19:11:03.662: INFO: starting to applying a network policy development/backend-allow-ingress-pod-label to only allow ingress access to app: webapp, role: backend pods in development namespace from pods in any namespace with the same labels
STEP: Ensuring we have ingress access from pods with matching labels
STEP: Ensuring we don't have ingress access from pods without matching labels
curl: (7) Failed to connect to 192.168.214.67 port 80: Connection timed out

STEP: Cleaning up after ourselves
Nov 19 19:13:16.110: INFO: starting to cleaning up network policy development/backend-allow-ingress-pod-label after ourselves
STEP: Applying a network policy to only allow ingress access to app: webapp role:backends in development namespace from pods with label app:webapp, role: frontendProd within namespace with label purpose: development
Nov 19 19:13:16.513: INFO: starting to applying a network policy development/backend-policy-allow-ingress-pod-namespace-label to only allow ingress access to app: webapp role:backends in development namespace from pods with label app:webapp, role: frontendProd within namespace with label purpose: development
STEP: Ensuring we don't have ingress access from role:frontend pods in production namespace
curl: (7) Failed to connect to 192.168.214.67 port 80: Connection timed out

STEP: Ensuring we have ingress access from role:frontend pods in development namespace
STEP: creating a Kubernetes client to the workload cluster
STEP: creating an HTTP deployment
STEP: waiting for deployment default/web-windowsjnfehz to be available
Nov 19 19:15:28.698: INFO: starting to wait for deployment to become available
Nov 19 19:16:49.809: INFO: Deployment default/web-windowsjnfehz is now available, took 1m21.111551163s
... skipping 51 lines ...
Nov 19 19:21:26.213: INFO: INFO: Collecting boot logs for AzureMachine capz-e2e-7afkwh-ha-md-0-tzkw2

Nov 19 19:21:26.640: INFO: INFO: Collecting logs for node 10.1.0.7 in cluster capz-e2e-7afkwh-ha in namespace capz-e2e-7afkwh

Nov 19 19:22:00.508: INFO: INFO: Collecting boot logs for AzureMachine capz-e2e-7afkwh-ha-md-win-9d6sl

Failed to get logs for machine capz-e2e-7afkwh-ha-md-win-9945f588f-596cz, cluster capz-e2e-7afkwh/capz-e2e-7afkwh-ha: [running command "get-eventlog -LogName Application -Source Docker | Select-Object Index, TimeGenerated, EntryType, Message | Sort-Object Index | Format-Table -Wrap -Autosize": Process exited with status 1, running command "docker ps -a": Process exited with status 1]
Nov 19 19:22:00.942: INFO: INFO: Collecting logs for node 10.1.0.5 in cluster capz-e2e-7afkwh-ha in namespace capz-e2e-7afkwh

Nov 19 19:22:36.130: INFO: INFO: Collecting boot logs for AzureMachine capz-e2e-7afkwh-ha-md-win-rtv45

Failed to get logs for machine capz-e2e-7afkwh-ha-md-win-9945f588f-bf2rn, cluster capz-e2e-7afkwh/capz-e2e-7afkwh-ha: [running command "get-eventlog -LogName Application -Source Docker | Select-Object Index, TimeGenerated, EntryType, Message | Sort-Object Index | Format-Table -Wrap -Autosize": Process exited with status 1, running command "docker ps -a": Process exited with status 1]
STEP: Dumping workload cluster capz-e2e-7afkwh/capz-e2e-7afkwh-ha kube-system pod logs
STEP: Creating log watcher for controller kube-system/calico-node-6tv6b, container calico-node
STEP: Creating log watcher for controller kube-system/etcd-capz-e2e-7afkwh-ha-control-plane-q2pfj, container etcd
STEP: Creating log watcher for controller kube-system/calico-node-xw6z9, container calico-node
STEP: Creating log watcher for controller kube-system/kube-apiserver-capz-e2e-7afkwh-ha-control-plane-q2pfj, container kube-apiserver
STEP: Creating log watcher for controller kube-system/calico-node-564st, container calico-node
... skipping 22 lines ...
STEP: Fetching kube-system pod logs took 957.898866ms
STEP: Dumping workload cluster capz-e2e-7afkwh/capz-e2e-7afkwh-ha Azure activity log
STEP: Creating log watcher for controller kube-system/kube-proxy-windows-znvhm, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-scheduler-capz-e2e-7afkwh-ha-control-plane-55gjr, container kube-scheduler
STEP: Creating log watcher for controller kube-system/kube-proxy-zbkll, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-bckr6, container kube-proxy
STEP: Error starting logs stream for pod kube-system/kube-proxy-windows-t69zp, container kube-proxy: container "kube-proxy" in pod "kube-proxy-windows-t69zp" is waiting to start: trying and failing to pull image
STEP: Error starting logs stream for pod kube-system/kube-proxy-windows-znvhm, container kube-proxy: container "kube-proxy" in pod "kube-proxy-windows-znvhm" is waiting to start: trying and failing to pull image
STEP: Got error while iterating over activity logs for resource group capz-e2e-7afkwh-ha: insights.ActivityLogsClient#listNextResults: Failure sending next results request: StatusCode=500 -- Original Error: context deadline exceeded
STEP: Fetching activity logs took 30.000507287s
STEP: Dumping all the Cluster API resources in the "capz-e2e-7afkwh" namespace
STEP: Deleting all clusters in the capz-e2e-7afkwh namespace
STEP: Deleting cluster capz-e2e-7afkwh-ha
INFO: Waiting for the Cluster capz-e2e-7afkwh/capz-e2e-7afkwh-ha to be deleted
STEP: Waiting for cluster capz-e2e-7afkwh-ha to be deleted
... skipping 14 lines ...
  Creates a public management cluster in the same vnet
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:144

INFO: "Creates a public management cluster in the same vnet" started at Fri, 19 Nov 2021 18:45:12 UTC on Ginkgo node 2 of 3
STEP: Creating namespace "capz-e2e-ephblo" for hosting the cluster
Nov 19 18:45:12.208: INFO: starting to create namespace for hosting the "capz-e2e-ephblo" test spec
2021/11/19 18:45:12 failed trying to get namespace (capz-e2e-ephblo):namespaces "capz-e2e-ephblo" not found
INFO: Creating namespace capz-e2e-ephblo
INFO: Creating event watcher for namespace "capz-e2e-ephblo"
Nov 19 18:45:12.252: INFO: Creating cluster identity secret
%!(EXTRA string=cluster-identity-secret)INFO: Cluster name is capz-e2e-ephblo-public-custom-vnet
STEP: creating Azure clients with the workload cluster's subscription
STEP: creating a resource group
... skipping 100 lines ...
STEP: Creating log watcher for controller kube-system/calico-node-cxbgn, container calico-node
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-m4tqf, container coredns
STEP: Creating log watcher for controller kube-system/calico-kube-controllers-846b5f484d-8rk56, container calico-kube-controllers
STEP: Creating log watcher for controller kube-system/kube-proxy-btthg, container kube-proxy
STEP: Creating log watcher for controller kube-system/etcd-capz-e2e-ephblo-public-custom-vnet-control-plane-9nbc5, container etcd
STEP: Creating log watcher for controller kube-system/kube-scheduler-capz-e2e-ephblo-public-custom-vnet-control-plane-9nbc5, container kube-scheduler
STEP: Got error while iterating over activity logs for resource group capz-e2e-ephblo-public-custom-vnet: insights.ActivityLogsClient#listNextResults: Failure sending next results request: StatusCode=500 -- Original Error: context deadline exceeded
STEP: Fetching activity logs took 30.000240997s
STEP: Dumping all the Cluster API resources in the "capz-e2e-ephblo" namespace
STEP: Deleting all clusters in the capz-e2e-ephblo namespace
STEP: Deleting cluster capz-e2e-ephblo-public-custom-vnet
INFO: Waiting for the Cluster capz-e2e-ephblo/capz-e2e-ephblo-public-custom-vnet to be deleted
STEP: Waiting for cluster capz-e2e-ephblo-public-custom-vnet to be deleted
W1119 19:33:02.112447   24478 reflector.go:441] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: watch of *v1.Event ended with: an error on the server ("unable to decode an event from the watch stream: http2: client connection lost") has prevented the request from succeeding
I1119 19:33:32.964567   24478 trace.go:205] Trace[980257331]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167 (19-Nov-2021 19:33:02.963) (total time: 30000ms):
Trace[980257331]: [30.000658693s] [30.000658693s] END
E1119 19:33:32.964626   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp 51.105.97.171:6443: i/o timeout
I1119 19:34:04.875419   24478 trace.go:205] Trace[2137793780]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167 (19-Nov-2021 19:33:34.873) (total time: 30001ms):
Trace[2137793780]: [30.001618261s] [30.001618261s] END
E1119 19:34:04.875481   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp 51.105.97.171:6443: i/o timeout
I1119 19:34:40.867230   24478 trace.go:205] Trace[1952431517]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167 (19-Nov-2021 19:34:10.865) (total time: 30001ms):
Trace[1952431517]: [30.001477507s] [30.001477507s] END
E1119 19:34:40.867302   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp 51.105.97.171:6443: i/o timeout
I1119 19:35:20.928828   24478 trace.go:205] Trace[1319418453]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167 (19-Nov-2021 19:34:50.927) (total time: 30001ms):
Trace[1319418453]: [30.001293437s] [30.001293437s] END
E1119 19:35:20.928897   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp 51.105.97.171:6443: i/o timeout
I1119 19:36:15.357877   24478 trace.go:205] Trace[1085217504]: "Reflector ListAndWatch" name:pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167 (19-Nov-2021 19:35:45.356) (total time: 30001ms):
Trace[1085217504]: [30.001257496s] [30.001257496s] END
E1119 19:36:15.357954   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp 51.105.97.171:6443: i/o timeout
STEP: Deleting namespace used for hosting the "create-workload-cluster" test spec
INFO: Deleting namespace capz-e2e-ephblo
STEP: Running additional cleanup for the "create-workload-cluster" test spec
Nov 19 19:36:48.118: INFO: deleting an existing virtual network "custom-vnet"
E1119 19:36:48.686605   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
Nov 19 19:36:58.972: INFO: deleting an existing route table "node-routetable"
Nov 19 19:37:10.255: INFO: deleting an existing network security group "node-nsg"
Nov 19 19:37:20.906: INFO: deleting an existing network security group "control-plane-nsg"
Nov 19 19:37:31.862: INFO: verifying the existing resource group "capz-e2e-ephblo-public-custom-vnet" is empty
Nov 19 19:37:31.904: INFO: deleting the existing resource group "capz-e2e-ephblo-public-custom-vnet"
E1119 19:37:38.331749   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 19:38:15.438361   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
STEP: Checking if any resources are left over in Azure for spec "create-workload-cluster"
STEP: Redacting sensitive information from logs
E1119 19:38:53.302402   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
INFO: "Creates a public management cluster in the same vnet" ran for 54m25s on Ginkgo node 2 of 3


• [SLOW TEST:3264.882 seconds]
Workload cluster creation
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:43
... skipping 6 lines ...
  with a 1 control plane nodes and 2 worker nodes
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:455

INFO: "with a 1 control plane nodes and 2 worker nodes" started at Fri, 19 Nov 2021 19:34:05 UTC on Ginkgo node 1 of 3
STEP: Creating namespace "capz-e2e-mkkq8f" for hosting the cluster
Nov 19 19:34:05.107: INFO: starting to create namespace for hosting the "capz-e2e-mkkq8f" test spec
2021/11/19 19:34:05 failed trying to get namespace (capz-e2e-mkkq8f):namespaces "capz-e2e-mkkq8f" not found
INFO: Creating namespace capz-e2e-mkkq8f
INFO: Creating event watcher for namespace "capz-e2e-mkkq8f"
Nov 19 19:34:05.141: INFO: Creating cluster identity secret
%!(EXTRA string=cluster-identity-secret)INFO: Cluster name is capz-e2e-mkkq8f-oot
INFO: Creating the workload cluster with name "capz-e2e-mkkq8f-oot" using the "external-cloud-provider" template (Kubernetes v1.22.4, 1 control-plane machines, 2 worker machines)
INFO: Getting the cluster template yaml
... skipping 53 lines ...
STEP: waiting for job default/curl-to-elb-jobpsgiu62e4l8 to be complete
Nov 19 19:43:11.231: INFO: waiting for job default/curl-to-elb-jobpsgiu62e4l8 to be complete
Nov 19 19:43:21.456: INFO: job default/curl-to-elb-jobpsgiu62e4l8 is complete, took 10.225102588s
STEP: connecting directly to the external LB service
Nov 19 19:43:21.456: INFO: starting attempts to connect directly to the external LB service
2021/11/19 19:43:21 [DEBUG] GET http://20.82.84.148
2021/11/19 19:43:51 [ERR] GET http://20.82.84.148 request failed: Get "http://20.82.84.148": dial tcp 20.82.84.148:80: i/o timeout
2021/11/19 19:43:51 [DEBUG] GET http://20.82.84.148: retrying in 1s (4 left)
Nov 19 19:43:52.679: INFO: successfully connected to the external LB service
STEP: deleting the test resources
Nov 19 19:43:52.679: INFO: starting to delete external LB service webdd6g1d-elb
Nov 19 19:43:52.831: INFO: starting to delete deployment webdd6g1d
Nov 19 19:43:52.950: INFO: starting to delete job curl-to-elb-jobpsgiu62e4l8
... skipping 34 lines ...
STEP: Fetching activity logs took 820.332881ms
STEP: Dumping all the Cluster API resources in the "capz-e2e-mkkq8f" namespace
STEP: Deleting all clusters in the capz-e2e-mkkq8f namespace
STEP: Deleting cluster capz-e2e-mkkq8f-oot
INFO: Waiting for the Cluster capz-e2e-mkkq8f/capz-e2e-mkkq8f-oot to be deleted
STEP: Waiting for cluster capz-e2e-mkkq8f-oot to be deleted
STEP: Got error while streaming logs for pod kube-system/calico-node-bzn69, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-6n7g4, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/cloud-node-manager-v4xmj, container cloud-node-manager: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-proxy-7pdxj, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/calico-node-rgdqf, container calico-node: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/cloud-node-manager-ksz99, container cloud-node-manager: http2: client connection lost
STEP: Deleting namespace used for hosting the "create-workload-cluster" test spec
INFO: Deleting namespace capz-e2e-mkkq8f
STEP: Checking if any resources are left over in Azure for spec "create-workload-cluster"
STEP: Redacting sensitive information from logs
INFO: "with a 1 control plane nodes and 2 worker nodes" ran for 17m18s on Ginkgo node 1 of 3

... skipping 10 lines ...
  with a single control plane node and 1 node
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:490

INFO: "with a single control plane node and 1 node" started at Fri, 19 Nov 2021 19:39:37 UTC on Ginkgo node 2 of 3
STEP: Creating namespace "capz-e2e-ks18xn" for hosting the cluster
Nov 19 19:39:37.093: INFO: starting to create namespace for hosting the "capz-e2e-ks18xn" test spec
2021/11/19 19:39:37 failed trying to get namespace (capz-e2e-ks18xn):namespaces "capz-e2e-ks18xn" not found
INFO: Creating namespace capz-e2e-ks18xn
INFO: Creating event watcher for namespace "capz-e2e-ks18xn"
Nov 19 19:39:37.132: INFO: Creating cluster identity secret
%!(EXTRA string=cluster-identity-secret)INFO: Cluster name is capz-e2e-ks18xn-aks
INFO: Creating the workload cluster with name "capz-e2e-ks18xn-aks" using the "aks-multi-tenancy" template (Kubernetes v1.19.13, 1 control-plane machines, 1 worker machines)
INFO: Getting the cluster template yaml
... skipping 7 lines ...
machinepool.cluster.x-k8s.io/agentpool1 created
azuremanagedmachinepool.infrastructure.cluster.x-k8s.io/agentpool1 created
azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity created

INFO: Waiting for the cluster infrastructure to be provisioned
STEP: Waiting for cluster to enter the provisioned phase
E1119 19:39:51.737977   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 19:40:43.831834   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 19:41:20.992801   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 19:41:52.268525   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 19:42:37.710792   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 19:43:23.097519   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
INFO: Waiting for control plane to be initialized
Nov 19 19:43:48.586: INFO: Waiting for the first control plane machine managed by capz-e2e-ks18xn/capz-e2e-ks18xn-aks to be provisioned
STEP: Waiting for atleast one control plane node to exist
E1119 19:43:57.833463   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
INFO: Waiting for control plane to be ready
Nov 19 19:43:58.620: INFO: Waiting for the first control plane machine managed by capz-e2e-ks18xn/capz-e2e-ks18xn-aks to be provisioned
STEP: Waiting for all control plane nodes to exist
INFO: Waiting for the machine deployments to be provisioned
INFO: Waiting for the machine pools to be provisioned
STEP: Waiting for the machine pool workload nodes to exist
... skipping 10 lines ...
STEP: time sync OK for host aks-agentpool1-28405750-vmss000000
STEP: time sync OK for host aks-agentpool1-28405750-vmss000000
STEP: Dumping logs from the "capz-e2e-ks18xn-aks" workload cluster
STEP: Dumping workload cluster capz-e2e-ks18xn/capz-e2e-ks18xn-aks logs
Nov 19 19:44:08.121: INFO: INFO: Collecting logs for node aks-agentpool1-28405750-vmss000000 in cluster capz-e2e-ks18xn-aks in namespace capz-e2e-ks18xn

E1119 19:44:29.440193   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 19:45:08.826966   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 19:45:42.597091   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
Nov 19 19:46:17.508: INFO: INFO: Collecting boot logs for VMSS instance 0 of scale set 0

Failed to get logs for machine pool agentpool0, cluster capz-e2e-ks18xn/capz-e2e-ks18xn-aks: [dialing public load balancer at capz-e2e-ks18xn-aks-7a8b8038.hcp.westeurope.azmk8s.io: dial tcp 20.76.61.9:22: connect: connection timed out, failed to get boot diagnostics data: compute.VirtualMachineScaleSetVMsClient#RetrieveBootDiagnosticsData: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="ParentResourceNotFound" Message="Can not perform requested operation on nested resource. Parent resource '0' not found."]
Nov 19 19:46:18.034: INFO: INFO: Collecting logs for node aks-agentpool1-28405750-vmss000000 in cluster capz-e2e-ks18xn-aks in namespace capz-e2e-ks18xn

E1119 19:46:25.799047   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 19:47:25.674330   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 19:48:03.921542   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
Nov 19 19:48:28.580: INFO: INFO: Collecting boot logs for VMSS instance 0 of scale set 0

Failed to get logs for machine pool agentpool1, cluster capz-e2e-ks18xn/capz-e2e-ks18xn-aks: [dialing public load balancer at capz-e2e-ks18xn-aks-7a8b8038.hcp.westeurope.azmk8s.io: dial tcp 20.76.61.9:22: connect: connection timed out, failed to get boot diagnostics data: compute.VirtualMachineScaleSetVMsClient#RetrieveBootDiagnosticsData: Failure responding to request: StatusCode=404 -- Original Error: autorest/azure: Service returned an error. Status=404 Code="ParentResourceNotFound" Message="Can not perform requested operation on nested resource. Parent resource '0' not found."]
STEP: Dumping workload cluster capz-e2e-ks18xn/capz-e2e-ks18xn-aks kube-system pod logs
STEP: Fetching kube-system pod logs took 1.059175512s
STEP: Dumping workload cluster capz-e2e-ks18xn/capz-e2e-ks18xn-aks Azure activity log
STEP: Creating log watcher for controller kube-system/coredns-84d976c568-h47wj, container coredns
STEP: Creating log watcher for controller kube-system/kube-proxy-gldtb, container kube-proxy
STEP: Creating log watcher for controller kube-system/kube-proxy-rzqn4, container kube-proxy
... skipping 8 lines ...
STEP: Fetching activity logs took 498.232574ms
STEP: Dumping all the Cluster API resources in the "capz-e2e-ks18xn" namespace
STEP: Deleting all clusters in the capz-e2e-ks18xn namespace
STEP: Deleting cluster capz-e2e-ks18xn-aks
INFO: Waiting for the Cluster capz-e2e-ks18xn/capz-e2e-ks18xn-aks to be deleted
STEP: Waiting for cluster capz-e2e-ks18xn-aks to be deleted
E1119 19:48:42.297486   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 19:49:30.000257   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 19:50:12.057274   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 19:51:00.280032   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 19:51:30.584146   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 19:52:08.722569   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 19:52:55.341125   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
STEP: Deleting namespace used for hosting the "create-workload-cluster" test spec
INFO: Deleting namespace capz-e2e-ks18xn
STEP: Checking if any resources are left over in Azure for spec "create-workload-cluster"
STEP: Redacting sensitive information from logs
E1119 19:53:53.636937   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
INFO: "with a single control plane node and 1 node" ran for 14m24s on Ginkgo node 2 of 3


• [SLOW TEST:863.672 seconds]
Workload cluster creation
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:43
... skipping 6 lines ...
  with a single control plane node and 1 node
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:413

INFO: "with a single control plane node and 1 node" started at Fri, 19 Nov 2021 19:33:20 UTC on Ginkgo node 3 of 3
STEP: Creating namespace "capz-e2e-cag9cs" for hosting the cluster
Nov 19 19:33:20.811: INFO: starting to create namespace for hosting the "capz-e2e-cag9cs" test spec
2021/11/19 19:33:20 failed trying to get namespace (capz-e2e-cag9cs):namespaces "capz-e2e-cag9cs" not found
INFO: Creating namespace capz-e2e-cag9cs
INFO: Creating event watcher for namespace "capz-e2e-cag9cs"
Nov 19 19:33:20.861: INFO: Creating cluster identity secret
%!(EXTRA string=cluster-identity-secret)INFO: Cluster name is capz-e2e-cag9cs-gpu
INFO: Creating the workload cluster with name "capz-e2e-cag9cs-gpu" using the "nvidia-gpu" template (Kubernetes v1.22.4, 1 control-plane machines, 1 worker machines)
INFO: Getting the cluster template yaml
... skipping 124 lines ...
  with a single control plane node and an Linux AzureMachinePool with 1 nodes and Windows AzureMachinePool with 1 node
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:579

INFO: "with a single control plane node and an Linux AzureMachinePool with 1 nodes and Windows AzureMachinePool with 1 node" started at Fri, 19 Nov 2021 19:54:00 UTC on Ginkgo node 2 of 3
STEP: Creating namespace "capz-e2e-tpqzgv" for hosting the cluster
Nov 19 19:54:00.768: INFO: starting to create namespace for hosting the "capz-e2e-tpqzgv" test spec
2021/11/19 19:54:00 failed trying to get namespace (capz-e2e-tpqzgv):namespaces "capz-e2e-tpqzgv" not found
INFO: Creating namespace capz-e2e-tpqzgv
INFO: Creating event watcher for namespace "capz-e2e-tpqzgv"
Nov 19 19:54:00.801: INFO: Creating cluster identity secret
%!(EXTRA string=cluster-identity-secret)INFO: Cluster name is capz-e2e-tpqzgv-win-vmss
INFO: Creating the workload cluster with name "capz-e2e-tpqzgv-win-vmss" using the "machine-pool-windows" template (Kubernetes v1.22.4, 1 control-plane machines, 1 worker machines)
INFO: Getting the cluster template yaml
... skipping 12 lines ...
kubeadmconfig.bootstrap.cluster.x-k8s.io/capz-e2e-tpqzgv-win-vmss-mp-win created
clusterresourceset.addons.cluster.x-k8s.io/capz-e2e-tpqzgv-win-vmss-flannel created
configmap/cni-capz-e2e-tpqzgv-win-vmss-flannel created

INFO: Waiting for the cluster infrastructure to be provisioned
STEP: Waiting for cluster to enter the provisioned phase
E1119 19:54:50.836851   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
INFO: Waiting for control plane to be initialized
INFO: Waiting for the first control plane machine managed by capz-e2e-tpqzgv/capz-e2e-tpqzgv-win-vmss-control-plane to be provisioned
STEP: Waiting for one control plane node to exist
E1119 19:55:47.354878   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 19:56:24.160409   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 19:57:12.488189   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
INFO: Waiting for control plane to be ready
INFO: Waiting for control plane capz-e2e-tpqzgv/capz-e2e-tpqzgv-win-vmss-control-plane to be ready (implies underlying nodes to be ready as well)
STEP: Waiting for the control plane to be ready
INFO: Waiting for the machine deployments to be provisioned
INFO: Waiting for the machine pools to be provisioned
STEP: Waiting for the machine pool workload nodes to exist
E1119 19:57:53.410943   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 19:58:52.676757   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
STEP: Waiting for the machine pool workload nodes to exist
E1119 19:59:23.271514   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 20:00:01.808128   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 20:00:44.662297   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 20:01:40.497460   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 20:02:26.065822   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
STEP: creating a Kubernetes client to the workload cluster
STEP: creating an HTTP deployment
STEP: waiting for deployment default/webay1i46 to be available
Nov 19 20:02:33.333: INFO: starting to wait for deployment to become available
Nov 19 20:02:53.691: INFO: Deployment default/webay1i46 is now available, took 20.358413387s
STEP: creating an internal Load Balancer service
Nov 19 20:02:53.691: INFO: starting to create an internal Load Balancer service
STEP: waiting for service default/webay1i46-ilb to be available
Nov 19 20:02:53.824: INFO: waiting for service default/webay1i46-ilb to be available
E1119 20:03:13.373057   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
Nov 19 20:03:44.502: INFO: service default/webay1i46-ilb is available, took 50.678038114s
STEP: connecting to the internal LB service from a curl pod
Nov 19 20:03:44.613: INFO: starting to create a curl to ilb job
STEP: waiting for job default/curl-to-ilb-jobwt6v3 to be complete
Nov 19 20:03:44.740: INFO: waiting for job default/curl-to-ilb-jobwt6v3 to be complete
E1119 20:03:54.124833   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
Nov 19 20:03:54.967: INFO: job default/curl-to-ilb-jobwt6v3 is complete, took 10.227339297s
STEP: deleting the ilb test resources
Nov 19 20:03:54.967: INFO: deleting the ilb service: webay1i46-ilb
Nov 19 20:03:55.104: INFO: deleting the ilb job: curl-to-ilb-jobwt6v3
STEP: creating an external Load Balancer service
Nov 19 20:03:55.222: INFO: starting to create an external Load Balancer service
STEP: waiting for service default/webay1i46-elb to be available
Nov 19 20:03:55.354: INFO: waiting for service default/webay1i46-elb to be available
E1119 20:04:30.970826   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 20:05:15.997379   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
Nov 19 20:05:16.375: INFO: service default/webay1i46-elb is available, took 1m21.021194389s
STEP: connecting to the external LB service from a curl pod
Nov 19 20:05:16.488: INFO: starting to create curl-to-elb job
STEP: waiting for job default/curl-to-elb-joblivex8bee49 to be complete
Nov 19 20:05:16.603: INFO: waiting for job default/curl-to-elb-joblivex8bee49 to be complete
Nov 19 20:05:26.827: INFO: job default/curl-to-elb-joblivex8bee49 is complete, took 10.223399893s
... skipping 6 lines ...
Nov 19 20:05:27.192: INFO: starting to delete deployment webay1i46
Nov 19 20:05:27.306: INFO: starting to delete job curl-to-elb-joblivex8bee49
STEP: creating a Kubernetes client to the workload cluster
STEP: creating an HTTP deployment
STEP: waiting for deployment default/web-windowsv7130c to be available
Nov 19 20:05:27.698: INFO: starting to wait for deployment to become available
E1119 20:05:52.852959   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 20:06:28.699871   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
Nov 19 20:06:58.898: INFO: Deployment default/web-windowsv7130c is now available, took 1m31.200162674s
STEP: creating an internal Load Balancer service
Nov 19 20:06:58.898: INFO: starting to create an internal Load Balancer service
STEP: waiting for service default/web-windowsv7130c-ilb to be available
Nov 19 20:06:59.038: INFO: waiting for service default/web-windowsv7130c-ilb to be available
E1119 20:07:18.683945   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
Nov 19 20:07:49.716: INFO: service default/web-windowsv7130c-ilb is available, took 50.678465011s
STEP: connecting to the internal LB service from a curl pod
Nov 19 20:07:49.828: INFO: starting to create a curl to ilb job
STEP: waiting for job default/curl-to-ilb-jobo78u4 to be complete
Nov 19 20:07:49.943: INFO: waiting for job default/curl-to-ilb-jobo78u4 to be complete
E1119 20:07:50.922680   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
Nov 19 20:08:00.166: INFO: job default/curl-to-ilb-jobo78u4 is complete, took 10.222960024s
STEP: deleting the ilb test resources
Nov 19 20:08:00.170: INFO: deleting the ilb service: web-windowsv7130c-ilb
Nov 19 20:08:00.316: INFO: deleting the ilb job: curl-to-ilb-jobo78u4
STEP: creating an external Load Balancer service
Nov 19 20:08:00.429: INFO: starting to create an external Load Balancer service
STEP: waiting for service default/web-windowsv7130c-elb to be available
Nov 19 20:08:00.561: INFO: waiting for service default/web-windowsv7130c-elb to be available
E1119 20:08:38.244296   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
Nov 19 20:09:21.592: INFO: service default/web-windowsv7130c-elb is available, took 1m21.031013313s
STEP: connecting to the external LB service from a curl pod
Nov 19 20:09:21.704: INFO: starting to create curl-to-elb job
STEP: waiting for job default/curl-to-elb-job7qxusi5rvin to be complete
Nov 19 20:09:21.820: INFO: waiting for job default/curl-to-elb-job7qxusi5rvin to be complete
E1119 20:09:28.822005   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
Nov 19 20:09:32.044: INFO: job default/curl-to-elb-job7qxusi5rvin is complete, took 10.223514478s
STEP: connecting directly to the external LB service
Nov 19 20:09:32.044: INFO: starting attempts to connect directly to the external LB service
2021/11/19 20:09:32 [DEBUG] GET http://20.50.218.103
Nov 19 20:09:32.266: INFO: successfully connected to the external LB service
STEP: deleting the test resources
... skipping 9 lines ...
Nov 19 20:09:47.734: INFO: INFO: Collecting logs for node capz-e2e-tpqzgv-win-vmss-mp-0000000 in cluster capz-e2e-tpqzgv-win-vmss in namespace capz-e2e-tpqzgv

Nov 19 20:09:58.612: INFO: INFO: Collecting boot logs for VMSS instance 0 of scale set capz-e2e-tpqzgv-win-vmss-mp-0

Nov 19 20:09:59.192: INFO: INFO: Collecting logs for node win-p-win000000 in cluster capz-e2e-tpqzgv-win-vmss in namespace capz-e2e-tpqzgv

E1119 20:10:07.663328   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
Nov 19 20:10:30.504: INFO: INFO: Collecting boot logs for VMSS instance 0 of scale set win-p-win

STEP: Dumping workload cluster capz-e2e-tpqzgv/capz-e2e-tpqzgv-win-vmss kube-system pod logs
STEP: Fetching kube-system pod logs took 773.822276ms
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-dhtxw, container coredns
STEP: Creating log watcher for controller kube-system/etcd-capz-e2e-tpqzgv-win-vmss-control-plane-9mcs6, container etcd
... skipping 5 lines ...
STEP: Creating log watcher for controller kube-system/coredns-78fcd69978-lsng4, container coredns
STEP: Creating log watcher for controller kube-system/kube-flannel-ds-amd64-tf7jb, container kube-flannel
STEP: Dumping workload cluster capz-e2e-tpqzgv/capz-e2e-tpqzgv-win-vmss Azure activity log
STEP: Creating log watcher for controller kube-system/kube-flannel-ds-amd64-vr8gq, container kube-flannel
STEP: Creating log watcher for controller kube-system/kube-flannel-ds-windows-amd64-svnfh, container kube-flannel
STEP: Creating log watcher for controller kube-system/kube-proxy-v95rx, container kube-proxy
E1119 20:10:51.672114   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
STEP: Got error while iterating over activity logs for resource group capz-e2e-tpqzgv-win-vmss: insights.ActivityLogsClient#listNextResults: Failure sending next results request: StatusCode=500 -- Original Error: context deadline exceeded
STEP: Fetching activity logs took 30.000434069s
STEP: Dumping all the Cluster API resources in the "capz-e2e-tpqzgv" namespace
STEP: Deleting all clusters in the capz-e2e-tpqzgv namespace
STEP: Deleting cluster capz-e2e-tpqzgv-win-vmss
INFO: Waiting for the Cluster capz-e2e-tpqzgv/capz-e2e-tpqzgv-win-vmss to be deleted
STEP: Waiting for cluster capz-e2e-tpqzgv-win-vmss to be deleted
E1119 20:11:47.994797   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
STEP: Got error while streaming logs for pod kube-system/kube-proxy-v95rx, container kube-proxy: http2: client connection lost
STEP: Got error while streaming logs for pod kube-system/kube-flannel-ds-amd64-vr8gq, container kube-flannel: http2: client connection lost
E1119 20:12:43.193652   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 20:13:40.532457   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 20:14:20.614090   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 20:15:16.318548   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 20:16:09.146384   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 20:17:07.534544   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 20:17:55.365067   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 20:18:47.588459   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 20:19:47.115221   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
STEP: Deleting namespace used for hosting the "create-workload-cluster" test spec
INFO: Deleting namespace capz-e2e-tpqzgv
STEP: Checking if any resources are left over in Azure for spec "create-workload-cluster"
STEP: Redacting sensitive information from logs
E1119 20:20:33.585955   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
E1119 20:21:31.302194   24478 reflector.go:138] pkg/mod/k8s.io/client-go@v0.22.2/tools/cache/reflector.go:167: Failed to watch *v1.Event: failed to list *v1.Event: Get "https://capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com:6443/api/v1/namespaces/capz-e2e-ephblo/events?resourceVersion=10279": dial tcp: lookup capz-e2e-ephblo-public-custom-vnet-faec5f63.westeurope.cloudapp.azure.com on 10.63.240.10:53: no such host
INFO: "with a single control plane node and an Linux AzureMachinePool with 1 nodes and Windows AzureMachinePool with 1 node" ran for 27m52s on Ginkgo node 2 of 3


• [SLOW TEST:1672.042 seconds]
Workload cluster creation
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:43
  Creating a Windows enabled VMSS cluster with dockershim
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:578
    with a single control plane node and an Linux AzureMachinePool with 1 nodes and Windows AzureMachinePool with 1 node
    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:579
------------------------------
{"component":"entrypoint","file":"prow/entrypoint/run.go:165","func":"k8s.io/test-infra/prow/entrypoint.Options.ExecuteProcess","level":"error","msg":"Process did not finish before 2h0m0s timeout","severity":"error","time":"2021-11-19T20:35:28Z"}
++ early_exit_handler
++ '[' -n 164 ']'
++ kill -TERM 164
++ cleanup_dind
++ [[ true == \t\r\u\e ]]
++ echo 'Cleaning up after docker'
... skipping 12 lines ...
Cleaning up after docker
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Stopping Docker: dockerProgram process in pidfile '/var/run/docker-ssd.pid', 1 process(es), refused to die.
================================================================================
Done cleaning up after docker in docker.
All sensitive variables are redacted
{"component":"entrypoint","file":"prow/entrypoint/run.go:255","func":"k8s.io/test-infra/prow/entrypoint.gracefullyTerminate","level":"error","msg":"Process did not exit before 15m0s grace period","severity":"error","time":"2021-11-19T20:50:28Z"}
{"component":"entrypoint","error":"os: process already finished","file":"prow/entrypoint/run.go:257","func":"k8s.io/test-infra/prow/entrypoint.gracefullyTerminate","level":"error","msg":"Could not kill process after grace period","severity":"error","time":"2021-11-19T20:50:28Z"}