This job view page is being replaced by Spyglass soon. Check out the new job view.
PRjackfrancis: helm gpu-operator instead of ClusterResourceSet
ResultFAILURE
Tests 1 failed / 26 succeeded
Started2023-01-26 03:13
Elapsed1h0m
Revisioncbc5593db41cf85e77f5bb760b8207cfcf56c80e
Refs 3099

Test Failures

capz-e2e [It] Workload cluster creation Creating a cluster that uses the external cloud provider and external azurediskcsi driver [OPTIONAL] with a 1 control plane nodes and 2 worker nodes 39m39s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\s\[It\]\sWorkload\scluster\screation\sCreating\sa\scluster\sthat\suses\sthe\sexternal\scloud\sprovider\sand\sexternal\sazurediskcsi\sdriver\s\[OPTIONAL\]\swith\sa\s1\scontrol\splane\snodes\sand\s2\sworker\snodes$'
[FAILED] Timed out after 1500.000s.
Timed out waiting for 2 nodes to be created for MachineDeployment capz-e2e-5a6ef3/capz-e2e-5a6ef3-oot-md-0
Expected
    <int>: 0
to equal
    <int>: 2
In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/machinedeployment_helpers.go:131 @ 01/26/23 03:56:08.552

				
				Click to see stdout/stderrfrom junit.e2e_suite.1.xml

Filter through log files | View test history on testgrid

Show 26 Passed Tests
Show 17 Skipped Tests

Error lines from build-log.txt

... skipping 628 lines ...
------------------------------
• [903.133 seconds]
Workload cluster creation Creating a Flatcar cluster [OPTIONAL] With Flatcar control-plane and worker nodes
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:321

  Captured StdOut/StdErr Output >>
  2023/01/26 03:24:28 failed trying to get namespace (capz-e2e-zs3uwq):namespaces "capz-e2e-zs3uwq" not found
  cluster.cluster.x-k8s.io/capz-e2e-zs3uwq-flatcar created
  azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-zs3uwq-flatcar created
  kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-zs3uwq-flatcar-control-plane created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-zs3uwq-flatcar-control-plane created
  machinedeployment.cluster.x-k8s.io/capz-e2e-zs3uwq-flatcar-md-0 created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-zs3uwq-flatcar-md-0 created
  kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/capz-e2e-zs3uwq-flatcar-md-0 created
  azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity-sp created

  felixconfiguration.crd.projectcalico.org/default configured

  Failed to get logs for Machine capz-e2e-zs3uwq-flatcar-control-plane-6v47s, Cluster capz-e2e-zs3uwq/capz-e2e-zs3uwq-flatcar: [dialing public load balancer at capz-e2e-zs3uwq-flatcar-1ea2f215.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.83.154:59462->20.13.97.25:22: read: connection reset by peer, dialing public load balancer at capz-e2e-zs3uwq-flatcar-1ea2f215.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.83.154:59464->20.13.97.25:22: read: connection reset by peer]
  Failed to get logs for Machine capz-e2e-zs3uwq-flatcar-md-0-568cfcb8b6-qlb6h, Cluster capz-e2e-zs3uwq/capz-e2e-zs3uwq-flatcar: [dialing public load balancer at capz-e2e-zs3uwq-flatcar-1ea2f215.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.83.154:58098->20.13.97.25:22: read: connection reset by peer, dialing public load balancer at capz-e2e-zs3uwq-flatcar-1ea2f215.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.83.154:58110->20.13.97.25:22: read: connection reset by peer, dialing public load balancer at capz-e2e-zs3uwq-flatcar-1ea2f215.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.83.154:58106->20.13.97.25:22: read: connection reset by peer, dialing public load balancer at capz-e2e-zs3uwq-flatcar-1ea2f215.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.83.154:58102->20.13.97.25:22: read: connection reset by peer, dialing public load balancer at capz-e2e-zs3uwq-flatcar-1ea2f215.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.83.154:58096->20.13.97.25:22: read: connection reset by peer, dialing public load balancer at capz-e2e-zs3uwq-flatcar-1ea2f215.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.83.154:58104->20.13.97.25:22: read: connection reset by peer, dialing public load balancer at capz-e2e-zs3uwq-flatcar-1ea2f215.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.83.154:58112->20.13.97.25:22: read: connection reset by peer, dialing public load balancer at capz-e2e-zs3uwq-flatcar-1ea2f215.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.83.154:58108->20.13.97.25:22: read: connection reset by peer, dialing public load balancer at capz-e2e-zs3uwq-flatcar-1ea2f215.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.83.154:58100->20.13.97.25:22: read: connection reset by peer]
  << Captured StdOut/StdErr Output

  Timeline >>
  INFO: "" started at Thu, 26 Jan 2023 03:24:27 UTC on Ginkgo node 10 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml
  STEP: Creating namespace "capz-e2e-zs3uwq" for hosting the cluster @ 01/26/23 03:24:27.998
  Jan 26 03:24:27.998: INFO: starting to create namespace for hosting the "capz-e2e-zs3uwq" test spec
... skipping 157 lines ...
------------------------------
• [1068.833 seconds]
Workload cluster creation Creating a cluster that uses the external cloud provider and machinepools [OPTIONAL] with 1 control plane node and 1 machinepool
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:575

  Captured StdOut/StdErr Output >>
  2023/01/26 03:24:28 failed trying to get namespace (capz-e2e-m7a47d):namespaces "capz-e2e-m7a47d" not found
  cluster.cluster.x-k8s.io/capz-e2e-m7a47d-flex created
  azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-m7a47d-flex created
  kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-m7a47d-flex-control-plane created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-m7a47d-flex-control-plane created
  machinepool.cluster.x-k8s.io/capz-e2e-m7a47d-flex-mp-0 created
  azuremachinepool.infrastructure.cluster.x-k8s.io/capz-e2e-m7a47d-flex-mp-0 created
... skipping 2 lines ...

  felixconfiguration.crd.projectcalico.org/default configured

  W0126 03:34:44.050091   37418 warnings.go:70] child pods are preserved by default when jobs are deleted; set propagationPolicy=Background to remove them or set propagationPolicy=Orphan to suppress this warning
  2023/01/26 03:35:35 [DEBUG] GET http://20.103.90.237
  W0126 03:36:19.372228   37418 warnings.go:70] child pods are preserved by default when jobs are deleted; set propagationPolicy=Background to remove them or set propagationPolicy=Orphan to suppress this warning
  Failed to get logs for MachinePool capz-e2e-m7a47d-flex-mp-0, Cluster capz-e2e-m7a47d/capz-e2e-m7a47d-flex: Unable to collect VMSS Boot Diagnostic logs: failed to parse resource id: parsing failed for /subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/resourceGroups/capz-e2e-m7a47d-flex/providers/Microsoft.Compute. Invalid resource Id format
  << Captured StdOut/StdErr Output

  Timeline >>
  INFO: "" started at Thu, 26 Jan 2023 03:24:27 UTC on Ginkgo node 8 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml
  STEP: Creating namespace "capz-e2e-m7a47d" for hosting the cluster @ 01/26/23 03:24:27.999
  Jan 26 03:24:27.999: INFO: starting to create namespace for hosting the "capz-e2e-m7a47d" test spec
... skipping 229 lines ...
------------------------------
• [1303.040 seconds]
Workload cluster creation Creating a GPU-enabled cluster [OPTIONAL] 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:506

  Captured StdOut/StdErr Output >>
  2023/01/26 03:24:28 failed trying to get namespace (capz-e2e-ayniet):namespaces "capz-e2e-ayniet" not found
  cluster.cluster.x-k8s.io/capz-e2e-ayniet-gpu created
  azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-ayniet-gpu created
  kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-ayniet-gpu-control-plane created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-ayniet-gpu-control-plane created
  azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity-sp created
  machinedeployment.cluster.x-k8s.io/capz-e2e-ayniet-gpu-md-0 created
... skipping 232 lines ...
------------------------------
• [1385.146 seconds]
Workload cluster creation Creating clusters using clusterclass [OPTIONAL] with a single control plane node, one linux worker node, and one windows worker node
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:908

  Captured StdOut/StdErr Output >>
  2023/01/26 03:24:28 failed trying to get namespace (capz-e2e-09zm69):namespaces "capz-e2e-09zm69" not found
  clusterclass.cluster.x-k8s.io/ci-default created
  kubeadmcontrolplanetemplate.controlplane.cluster.x-k8s.io/ci-default-kubeadm-control-plane created
  azureclustertemplate.infrastructure.cluster.x-k8s.io/ci-default-azure-cluster created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/ci-default-control-plane created
  kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/ci-default-worker created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/ci-default-worker created
... skipping 5 lines ...
  clusterresourceset.addons.cluster.x-k8s.io/csi-proxy created
  configmap/cni-capz-e2e-09zm69-cc-calico-windows created
  configmap/csi-proxy-addon created

  felixconfiguration.crd.projectcalico.org/default configured

  Failed to get logs for Machine capz-e2e-09zm69-cc-jf7ww-v8w2d, Cluster capz-e2e-09zm69/capz-e2e-09zm69-cc: dialing public load balancer at capz-e2e-09zm69-cc-ab4a6fa1.westeurope.cloudapp.azure.com: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
  Failed to get logs for Machine capz-e2e-09zm69-cc-md-0-2cl7g-648d686b8-4wcj4, Cluster capz-e2e-09zm69/capz-e2e-09zm69-cc: dialing public load balancer at capz-e2e-09zm69-cc-ab4a6fa1.westeurope.cloudapp.azure.com: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
  Failed to get logs for Machine capz-e2e-09zm69-cc-md-win-pfz64-599746bc-dk6b2, Cluster capz-e2e-09zm69/capz-e2e-09zm69-cc: dialing public load balancer at capz-e2e-09zm69-cc-ab4a6fa1.westeurope.cloudapp.azure.com: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
  << Captured StdOut/StdErr Output

  Timeline >>
  INFO: "" started at Thu, 26 Jan 2023 03:24:28 UTC on Ginkgo node 3 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml
  STEP: Creating namespace "capz-e2e-09zm69" for hosting the cluster @ 01/26/23 03:24:28.002
  Jan 26 03:24:28.002: INFO: starting to create namespace for hosting the "capz-e2e-09zm69" test spec
... skipping 186 lines ...
  Jan 26 03:39:52.747: INFO: Collecting events for Pod kube-system/kube-proxy-wwz8m
  Jan 26 03:39:52.747: INFO: Creating log watcher for controller kube-system/csi-proxy-c954c, container csi-proxy
  Jan 26 03:39:53.019: INFO: Fetching kube-system pod logs took 1.732809569s
  Jan 26 03:39:53.019: INFO: Dumping workload cluster capz-e2e-09zm69/capz-e2e-09zm69-cc Azure activity log
  Jan 26 03:39:53.019: INFO: Creating log watcher for controller tigera-operator/tigera-operator-65d6bf4d4f-bkcgt, container tigera-operator
  Jan 26 03:39:53.020: INFO: Collecting events for Pod tigera-operator/tigera-operator-65d6bf4d4f-bkcgt
  Jan 26 03:39:53.040: INFO: Error fetching activity logs for cluster capz-e2e-09zm69-cc in namespace capz-e2e-09zm69.  Not able to find the AzureManagedControlPlane on the management cluster: azuremanagedcontrolplanes.infrastructure.cluster.x-k8s.io "capz-e2e-09zm69-cc" not found
  Jan 26 03:39:53.040: INFO: Fetching activity logs took 21.260736ms
  Jan 26 03:39:53.040: INFO: Dumping all the Cluster API resources in the "capz-e2e-09zm69" namespace
  Jan 26 03:39:53.406: INFO: Deleting all clusters in the capz-e2e-09zm69 namespace
  STEP: Deleting cluster capz-e2e-09zm69-cc @ 01/26/23 03:39:53.423
  INFO: Waiting for the Cluster capz-e2e-09zm69/capz-e2e-09zm69-cc to be deleted
  STEP: Waiting for cluster capz-e2e-09zm69-cc to be deleted @ 01/26/23 03:39:53.434
... skipping 10 lines ...
------------------------------
• [1497.082 seconds]
Workload cluster creation Creating a dual-stack cluster [OPTIONAL] With dual-stack worker node
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:832

  Captured StdOut/StdErr Output >>
  2023/01/26 03:24:28 failed trying to get namespace (capz-e2e-2upwju):namespaces "capz-e2e-2upwju" not found
  cluster.cluster.x-k8s.io/capz-e2e-2upwju-dual-stack created
  azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-2upwju-dual-stack created
  kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-2upwju-dual-stack-control-plane created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-2upwju-dual-stack-control-plane created
  azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity-sp created
  machinedeployment.cluster.x-k8s.io/capz-e2e-2upwju-dual-stack-md-0 created
... skipping 325 lines ...
  << Timeline
------------------------------
[SynchronizedAfterSuite] PASSED [0.000 seconds]
[SynchronizedAfterSuite] 
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/e2e_suite_test.go:116
------------------------------
• [FAILED] [2379.721 seconds]
Workload cluster creation Creating a cluster that uses the external cloud provider and external azurediskcsi driver [OPTIONAL] [It] 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:639

  Captured StdOut/StdErr Output >>
  2023/01/26 03:24:28 failed trying to get namespace (capz-e2e-5a6ef3):namespaces "capz-e2e-5a6ef3" not found
  cluster.cluster.x-k8s.io/capz-e2e-5a6ef3-oot created
  azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-5a6ef3-oot created
  kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-5a6ef3-oot-control-plane created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-5a6ef3-oot-control-plane created
  machinedeployment.cluster.x-k8s.io/capz-e2e-5a6ef3-oot-md-0 created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-5a6ef3-oot-md-0 created
... skipping 90 lines ...
  INFO: Waiting for control plane to be ready
  INFO: Waiting for control plane capz-e2e-5a6ef3/capz-e2e-5a6ef3-oot-control-plane to be ready (implies underlying nodes to be ready as well)
  STEP: Waiting for the control plane to be ready @ 01/26/23 03:31:08.524
  STEP: Checking all the control plane machines are in the expected failure domains @ 01/26/23 03:31:08.53
  INFO: Waiting for the machine deployments to be provisioned
  STEP: Waiting for the workload nodes to exist @ 01/26/23 03:31:08.551
  [FAILED] in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/machinedeployment_helpers.go:131 @ 01/26/23 03:56:08.552
  Jan 26 03:56:08.552: INFO: FAILED!
  Jan 26 03:56:08.552: INFO: Cleaning up after "Workload cluster creation Creating a cluster that uses the external cloud provider and external azurediskcsi driver [OPTIONAL] with a 1 control plane nodes and 2 worker nodes" spec
  STEP: Dumping logs from the "capz-e2e-5a6ef3-oot" workload cluster @ 01/26/23 03:56:08.552
  Jan 26 03:56:08.552: INFO: Dumping workload cluster capz-e2e-5a6ef3/capz-e2e-5a6ef3-oot logs
  Jan 26 03:56:08.597: INFO: Collecting logs for Linux node capz-e2e-5a6ef3-oot-control-plane-5rtfl in cluster capz-e2e-5a6ef3-oot in namespace capz-e2e-5a6ef3

  Jan 26 03:56:25.545: INFO: Collecting boot logs for AzureMachine capz-e2e-5a6ef3-oot-control-plane-5rtfl
... skipping 63 lines ...
  INFO: Deleting namespace capz-e2e-5a6ef3
  Jan 26 04:02:44.448: INFO: Checking if any resources are left over in Azure for spec "create-workload-cluster"
  STEP: Redacting sensitive information from logs @ 01/26/23 04:02:45.06
  INFO: "with a 1 control plane nodes and 2 worker nodes" started at Thu, 26 Jan 2023 04:04:07 UTC on Ginkgo node 4 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml
  << Timeline

  [FAILED] Timed out after 1500.000s.
  Timed out waiting for 2 nodes to be created for MachineDeployment capz-e2e-5a6ef3/capz-e2e-5a6ef3-oot-md-0
  Expected
      <int>: 0
  to equal
      <int>: 2
  In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/machinedeployment_helpers.go:131 @ 01/26/23 03:56:08.552
... skipping 14 lines ...
------------------------------
• [2817.706 seconds]
Workload cluster creation Creating a private cluster [OPTIONAL] Creates a public management cluster in a custom vnet
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:156

  Captured StdOut/StdErr Output >>
  2023/01/26 03:24:27 failed trying to get namespace (capz-e2e-xwo60y):namespaces "capz-e2e-xwo60y" not found
  cluster.cluster.x-k8s.io/capz-e2e-xwo60y-public-custom-vnet created
  azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-xwo60y-public-custom-vnet created
  kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-xwo60y-public-custom-vnet-control-plane created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-xwo60y-public-custom-vnet-control-plane created
  machinedeployment.cluster.x-k8s.io/capz-e2e-xwo60y-public-custom-vnet-md-0 created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-xwo60y-public-custom-vnet-md-0 created
... skipping 247 lines ...
  Jan 26 04:05:10.289: INFO: Collecting events for Pod kube-system/kube-scheduler-capz-e2e-xwo60y-public-custom-vnet-control-plane-4nsbp
  Jan 26 04:05:10.290: INFO: Collecting events for Pod kube-system/kube-proxy-sppdw
  Jan 26 04:05:10.408: INFO: Fetching kube-system pod logs took 1.667169409s
  Jan 26 04:05:10.408: INFO: Dumping workload cluster capz-e2e-xwo60y/capz-e2e-xwo60y-public-custom-vnet Azure activity log
  Jan 26 04:05:10.408: INFO: Creating log watcher for controller tigera-operator/tigera-operator-65d6bf4d4f-j8mgc, container tigera-operator
  Jan 26 04:05:10.409: INFO: Collecting events for Pod tigera-operator/tigera-operator-65d6bf4d4f-j8mgc
  Jan 26 04:05:18.466: INFO: Got error while iterating over activity logs for resource group capz-e2e-xwo60y-public-custom-vnet: insights.ActivityLogsClient#listNextResults: Failure responding to next results request: StatusCode=404 -- Original Error: autorest/azure: error response cannot be parsed: {"<!DOCTYPE html PUBLIC \"-//W3C//DTD XHTML 1.0 Strict//EN\" \"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd\">\r\n<html xmlns=\"http://www.w3.org/1999/xhtml\">\r\n<head>\r\n<meta http-equiv=\"Content-Type\" content=\"text/html; charset=iso-8859-1\"/>\r\n<title>404 - File or directory not found.</title>\r\n<style type=\"text/css\">\r\n<!--\r\nbody{margin:0;font-size:.7em;font-family:Verdana, Arial, Helvetica, sans-serif;background:#EEEEEE;}\r\nfieldset{padding:0 15px 10px 15px;} \r\nh1{font-size:2.4em;margin:0;color:#FFF;}\r\nh2{font-si" '\x00' '\x00'} error: invalid character '<' looking for beginning of value
  Jan 26 04:05:18.466: INFO: Fetching activity logs took 8.0577707s
  Jan 26 04:05:18.466: INFO: Dumping all the Cluster API resources in the "capz-e2e-xwo60y" namespace
  Jan 26 04:05:18.764: INFO: Deleting all clusters in the capz-e2e-xwo60y namespace
  STEP: Deleting cluster capz-e2e-xwo60y-public-custom-vnet @ 01/26/23 04:05:18.785
  INFO: Waiting for the Cluster capz-e2e-xwo60y/capz-e2e-xwo60y-public-custom-vnet to be deleted
  STEP: Waiting for cluster capz-e2e-xwo60y-public-custom-vnet to be deleted @ 01/26/23 04:05:18.797
  INFO: Got error while streaming logs for pod capi-kubeadm-control-plane-system/capi-kubeadm-control-plane-controller-manager-66576dfdb7-jdzfk, container manager: http2: client connection lost
  INFO: Got error while streaming logs for pod capi-system/capi-controller-manager-768b7b88f9-hqmhn, container manager: http2: client connection lost
  INFO: Got error while streaming logs for pod capz-system/capz-controller-manager-54c5b7f555-d6p9h, container manager: http2: client connection lost
  INFO: Got error while streaming logs for pod capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager-8ddf45bf4-7pfqq, container manager: http2: client connection lost
  Jan 26 04:07:58.882: INFO: Deleting namespace used for hosting the "create-workload-cluster" test spec
  INFO: Deleting namespace capz-e2e-xwo60y
  Jan 26 04:07:58.900: INFO: Running additional cleanup for the "create-workload-cluster" test spec
  Jan 26 04:07:58.900: INFO: deleting an existing virtual network "custom-vnet"
  Jan 26 04:08:10.107: INFO: deleting an existing route table "node-routetable"
  Jan 26 04:08:13.385: INFO: deleting an existing network security group "node-nsg"
... skipping 16 lines ...
[ReportAfterSuite] PASSED [0.017 seconds]
[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report
autogenerated by Ginkgo
------------------------------

Summarizing 1 Failure:
  [FAIL] Workload cluster creation Creating a cluster that uses the external cloud provider and external azurediskcsi driver [OPTIONAL] [It] with a 1 control plane nodes and 2 worker nodes
  /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/machinedeployment_helpers.go:131

Ran 7 of 24 Specs in 2999.136 seconds
FAIL! -- 6 Passed | 1 Failed | 0 Pending | 17 Skipped

You're using deprecated Ginkgo functionality:
=============================================
  CurrentGinkgoTestDescription() is deprecated in Ginkgo V2.  Use CurrentSpecReport() instead.
  Learn more at: https://onsi.github.io/ginkgo/MIGRATING_TO_V2#changed-currentginkgotestdescription
    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:427
... skipping 43 lines ...
    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:285
    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:427

To silence deprecations that can be silenced set the following environment variable:
  ACK_GINKGO_DEPRECATIONS=2.7.0

--- FAIL: TestE2E (2559.78s)
FAIL

You're using deprecated Ginkgo functionality:
=============================================
  CurrentGinkgoTestDescription() is deprecated in Ginkgo V2.  Use CurrentSpecReport() instead.
  Learn more at: https://onsi.github.io/ginkgo/MIGRATING_TO_V2#changed-currentginkgotestdescription
    /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:427
... skipping 34 lines ...

PASS


Ginkgo ran 1 suite in 53m51.388867468s

Test Suite Failed
make[1]: *** [Makefile:654: test-e2e-run] Error 1
make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure'
make: *** [Makefile:663: 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 ...