This job view page is being replaced by Spyglass soon. Check out the new job view.
PRjackfrancis: E2E: use a common cluster-identity-secret
ResultFAILURE
Tests 1 failed / 26 succeeded
Started2023-01-23 23:17
Elapsed1h18m
Revisionbc0386b8b11ed2532565fd131a83e7b0e167123a
Refs 3075

Test Failures

capz-e2e [It] Workload cluster creation Creating a GPU-enabled cluster [OPTIONAL] with a single control plane node and 1 node 58m36s

go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\s\[It\]\sWorkload\scluster\screation\sCreating\sa\sGPU\-enabled\scluster\s\[OPTIONAL\]\swith\sa\ssingle\scontrol\splane\snode\sand\s1\snode$'
[FAILED] Timed out after 1800.001s.
Timed out waiting for 1 nodes to be created for MachineDeployment capz-e2e-1fstlz/capz-e2e-1fstlz-gpu-md-0
Expected
    <int>: 0
to equal
    <int>: 1
In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/machinedeployment_helpers.go:131 @ 01/24/23 00:11:51.411

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

Filter through log files | View test history on testgrid

Show 26 Passed Tests
Show 20 Skipped Tests

Error lines from build-log.txt

... skipping 632 lines ...
------------------------------
• [1116.808 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:573

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

  felixconfiguration.crd.projectcalico.org/default configured

  W0123 23:46:15.293535   37439 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/23 23:46:46 [DEBUG] GET http://20.71.67.115
  W0123 23:47:21.094112   37439 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-4s66pq-flex-mp-0, Cluster capz-e2e-4s66pq/capz-e2e-4s66pq-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-4s66pq-flex/providers/Microsoft.Compute. Invalid resource Id format
  << Captured StdOut/StdErr Output

  Timeline >>
  INFO: "" started at Mon, 23 Jan 2023 23:34:28 UTC on Ginkgo node 2 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml
  STEP: Creating namespace "capz-e2e-4s66pq" for hosting the cluster @ 01/23/23 23:34:28.952
  Jan 23 23:34:28.952: INFO: starting to create namespace for hosting the "capz-e2e-4s66pq" test spec
... skipping 229 lines ...
------------------------------
• [1156.580 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/23 23:34:28 failed trying to get namespace (capz-e2e-fiiwth):namespaces "capz-e2e-fiiwth" not found
  cluster.cluster.x-k8s.io/capz-e2e-fiiwth-flatcar created
  azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-fiiwth-flatcar created
  kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-fiiwth-flatcar-control-plane created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-fiiwth-flatcar-control-plane created
  machinedeployment.cluster.x-k8s.io/capz-e2e-fiiwth-flatcar-md-0 created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-fiiwth-flatcar-md-0 created
  kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/capz-e2e-fiiwth-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-fiiwth-flatcar-control-plane-b6gzr, Cluster capz-e2e-fiiwth/capz-e2e-fiiwth-flatcar: [dialing public load balancer at capz-e2e-fiiwth-flatcar-5d2cafc5.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.44.12:53490->20.238.254.30:22: read: connection reset by peer, dialing public load balancer at capz-e2e-fiiwth-flatcar-5d2cafc5.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.44.12:53506->20.238.254.30:22: read: connection reset by peer]
  Failed to get logs for Machine capz-e2e-fiiwth-flatcar-md-0-5975bb9776-2nx7q, Cluster capz-e2e-fiiwth/capz-e2e-fiiwth-flatcar: [dialing public load balancer at capz-e2e-fiiwth-flatcar-5d2cafc5.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.44.12:48878->20.238.254.30:22: read: connection reset by peer, dialing public load balancer at capz-e2e-fiiwth-flatcar-5d2cafc5.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.44.12:48890->20.238.254.30:22: read: connection reset by peer, dialing public load balancer at capz-e2e-fiiwth-flatcar-5d2cafc5.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.44.12:48894->20.238.254.30:22: read: connection reset by peer, dialing public load balancer at capz-e2e-fiiwth-flatcar-5d2cafc5.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.44.12:48888->20.238.254.30:22: read: connection reset by peer, dialing public load balancer at capz-e2e-fiiwth-flatcar-5d2cafc5.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.44.12:48886->20.238.254.30:22: read: connection reset by peer, dialing public load balancer at capz-e2e-fiiwth-flatcar-5d2cafc5.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.44.12:48880->20.238.254.30:22: read: connection reset by peer, dialing public load balancer at capz-e2e-fiiwth-flatcar-5d2cafc5.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.44.12:48904->20.238.254.30:22: read: connection reset by peer, dialing public load balancer at capz-e2e-fiiwth-flatcar-5d2cafc5.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.44.12:48902->20.238.254.30:22: read: connection reset by peer, dialing public load balancer at capz-e2e-fiiwth-flatcar-5d2cafc5.westeurope.cloudapp.azure.com: ssh: handshake failed: read tcp 10.60.44.12:48896->20.238.254.30:22: read: connection reset by peer]
  << Captured StdOut/StdErr Output

  Timeline >>
  INFO: "" started at Mon, 23 Jan 2023 23:34:28 UTC on Ginkgo node 4 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml
  STEP: Creating namespace "capz-e2e-fiiwth" for hosting the cluster @ 01/23/23 23:34:28.937
  Jan 23 23:34:28.937: INFO: starting to create namespace for hosting the "capz-e2e-fiiwth" test spec
... skipping 157 lines ...
------------------------------
• [1300.373 seconds]
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
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:637

  Captured StdOut/StdErr Output >>
  2023/01/23 23:34:29 failed trying to get namespace (capz-e2e-5rucxy):namespaces "capz-e2e-5rucxy" not found
  cluster.cluster.x-k8s.io/capz-e2e-5rucxy-oot created
  azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-5rucxy-oot created
  kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-5rucxy-oot-control-plane created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-5rucxy-oot-control-plane created
  machinedeployment.cluster.x-k8s.io/capz-e2e-5rucxy-oot-md-0 created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-5rucxy-oot-md-0 created
  kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/capz-e2e-5rucxy-oot-md-0 created
  azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity-sp created

  felixconfiguration.crd.projectcalico.org/default configured

  W0123 23:46:04.667030   37443 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/23 23:47:05 [DEBUG] GET http://20.71.69.23
  2023/01/23 23:47:35 [ERR] GET http://20.71.69.23 request failed: Get "http://20.71.69.23": dial tcp 20.71.69.23:80: i/o timeout
  2023/01/23 23:47:35 [DEBUG] GET http://20.71.69.23: retrying in 1s (4 left)
  2023/01/23 23:48:06 [ERR] GET http://20.71.69.23 request failed: Get "http://20.71.69.23": dial tcp 20.71.69.23:80: i/o timeout
  2023/01/23 23:48:06 [DEBUG] GET http://20.71.69.23: retrying in 2s (3 left)
  W0123 23:49:05.545598   37443 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
  << Captured StdOut/StdErr Output

  Timeline >>
  INFO: "" started at Mon, 23 Jan 2023 23:34:28 UTC on Ginkgo node 5 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml
... skipping 272 lines ...
------------------------------
• [1439.604 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:896

  Captured StdOut/StdErr Output >>
  2023/01/23 23:34:29 failed trying to get namespace (capz-e2e-97qzmt):namespaces "capz-e2e-97qzmt" 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-97qzmt-cc-calico-windows created
  configmap/csi-proxy-addon created

  felixconfiguration.crd.projectcalico.org/default configured

  Failed to get logs for Machine capz-e2e-97qzmt-cc-md-0-57n4k-5d8f57fc84-w6lx8, Cluster capz-e2e-97qzmt/capz-e2e-97qzmt-cc: dialing public load balancer at capz-e2e-97qzmt-cc-78236fb5.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-97qzmt-cc-md-win-pqsh6-7d4f566d69-vs4mt, Cluster capz-e2e-97qzmt/capz-e2e-97qzmt-cc: dialing public load balancer at capz-e2e-97qzmt-cc-78236fb5.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-97qzmt-cc-pj8m4-tdkvr, Cluster capz-e2e-97qzmt/capz-e2e-97qzmt-cc: dialing public load balancer at capz-e2e-97qzmt-cc-78236fb5.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 Mon, 23 Jan 2023 23:34:28 UTC on Ginkgo node 6 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml
  STEP: Creating namespace "capz-e2e-97qzmt" for hosting the cluster @ 01/23/23 23:34:28.967
  Jan 23 23:34:28.967: INFO: starting to create namespace for hosting the "capz-e2e-97qzmt" test spec
... skipping 186 lines ...
  Jan 23 23:52:01.970: INFO: Collecting events for Pod kube-system/kube-scheduler-capz-e2e-97qzmt-cc-control-plane-7l4hk-fsrcf
  Jan 23 23:52:01.971: INFO: Creating log watcher for controller kube-system/csi-azuredisk-controller-545d478dbf-p9j4s, container csi-resizer
  Jan 23 23:52:02.236: INFO: Fetching kube-system pod logs took 1.756793971s
  Jan 23 23:52:02.236: INFO: Dumping workload cluster capz-e2e-97qzmt/capz-e2e-97qzmt-cc Azure activity log
  Jan 23 23:52:02.236: INFO: Creating log watcher for controller tigera-operator/tigera-operator-65d6bf4d4f-nw6sm, container tigera-operator
  Jan 23 23:52:02.236: INFO: Collecting events for Pod tigera-operator/tigera-operator-65d6bf4d4f-nw6sm
  Jan 23 23:52:02.265: INFO: Error fetching activity logs for cluster capz-e2e-97qzmt-cc in namespace capz-e2e-97qzmt.  Not able to find the AzureManagedControlPlane on the management cluster: azuremanagedcontrolplanes.infrastructure.cluster.x-k8s.io "capz-e2e-97qzmt-cc" not found
  Jan 23 23:52:02.265: INFO: Fetching activity logs took 29.258405ms
  Jan 23 23:52:02.265: INFO: Dumping all the Cluster API resources in the "capz-e2e-97qzmt" namespace
  Jan 23 23:52:02.738: INFO: Deleting all clusters in the capz-e2e-97qzmt namespace
  STEP: Deleting cluster capz-e2e-97qzmt-cc @ 01/23/23 23:52:02.768
  INFO: Waiting for the Cluster capz-e2e-97qzmt/capz-e2e-97qzmt-cc to be deleted
  STEP: Waiting for cluster capz-e2e-97qzmt-cc to be deleted @ 01/23/23 23:52:02.79
... skipping 10 lines ...
------------------------------
• [1705.674 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:820

  Captured StdOut/StdErr Output >>
  2023/01/23 23:34:29 failed trying to get namespace (capz-e2e-3s91gu):namespaces "capz-e2e-3s91gu" not found
  cluster.cluster.x-k8s.io/capz-e2e-3s91gu-dual-stack created
  azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-3s91gu-dual-stack created
  kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-3s91gu-dual-stack-control-plane created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-3s91gu-dual-stack-control-plane created
  azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity-sp created
  machinedeployment.cluster.x-k8s.io/capz-e2e-3s91gu-dual-stack-md-0 created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-3s91gu-dual-stack-md-0 created
  kubeadmconfigtemplate.bootstrap.cluster.x-k8s.io/capz-e2e-3s91gu-dual-stack-md-0 created

  felixconfiguration.crd.projectcalico.org/default configured

  W0123 23:48:45.286238   37440 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/23 23:49:26 [DEBUG] GET http://20.71.69.51
  2023/01/23 23:49:56 [ERR] GET http://20.71.69.51 request failed: Get "http://20.71.69.51": dial tcp 20.71.69.51:80: i/o timeout
  2023/01/23 23:49:56 [DEBUG] GET http://20.71.69.51: retrying in 1s (4 left)
  W0123 23:50:41.232284   37440 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
  W0123 23:51:45.428318   37440 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
  W0123 23:52:54.918755   37440 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
  << Captured StdOut/StdErr Output

... skipping 320 lines ...
------------------------------
• [3130.940 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/23 23:34:28 failed trying to get namespace (capz-e2e-sqza4k):namespaces "capz-e2e-sqza4k" not found
  cluster.cluster.x-k8s.io/capz-e2e-sqza4k-public-custom-vnet created
  azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-sqza4k-public-custom-vnet created
  kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-sqza4k-public-custom-vnet-control-plane created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-sqza4k-public-custom-vnet-control-plane created
  machinedeployment.cluster.x-k8s.io/capz-e2e-sqza4k-public-custom-vnet-md-0 created
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-sqza4k-public-custom-vnet-md-0 created
... skipping 255 lines ...
  Jan 24 00:20:11.242: INFO: Fetching activity logs took 10.064639068s
  Jan 24 00:20:11.242: INFO: Dumping all the Cluster API resources in the "capz-e2e-sqza4k" namespace
  Jan 24 00:20:11.925: INFO: Deleting all clusters in the capz-e2e-sqza4k namespace
  STEP: Deleting cluster capz-e2e-sqza4k-public-custom-vnet @ 01/24/23 00:20:11.967
  INFO: Waiting for the Cluster capz-e2e-sqza4k/capz-e2e-sqza4k-public-custom-vnet to be deleted
  STEP: Waiting for cluster capz-e2e-sqza4k-public-custom-vnet to be deleted @ 01/24/23 00:20:11.995
  INFO: Got error while streaming logs for pod capz-system/capz-controller-manager-cc4f4b875-gc4cs, container manager: http2: client connection lost
  INFO: Got error while streaming logs for pod capi-kubeadm-bootstrap-system/capi-kubeadm-bootstrap-controller-manager-8ddf45bf4-xtfmt, container manager: http2: client connection lost
  INFO: Got error while streaming logs for pod capi-kubeadm-control-plane-system/capi-kubeadm-control-plane-controller-manager-66576dfdb7-wtt68, container manager: http2: client connection lost
  INFO: Got error while streaming logs for pod capi-system/capi-controller-manager-768b7b88f9-64n7t, container manager: http2: client connection lost
  Jan 24 00:23:12.133: INFO: Deleting namespace used for hosting the "create-workload-cluster" test spec
  INFO: Deleting namespace capz-e2e-sqza4k
  Jan 24 00:23:12.170: INFO: Running additional cleanup for the "create-workload-cluster" test spec
  Jan 24 00:23:12.170: INFO: deleting an existing virtual network "custom-vnet"
  Jan 24 00:23:23.768: INFO: deleting an existing route table "node-routetable"
  Jan 24 00:23:27.097: INFO: deleting an existing network security group "node-nsg"
... skipping 2 lines ...
  Jan 24 00:23:49.995: INFO: deleting the existing resource group "capz-e2e-sqza4k-public-custom-vnet"
  Jan 24 00:25:08.662: INFO: Checking if any resources are left over in Azure for spec "create-workload-cluster"
  STEP: Redacting sensitive information from logs @ 01/24/23 00:25:09.032
  INFO: "Creates a public management cluster in a custom vnet" started at Tue, 24 Jan 2023 00:26:39 UTC on Ginkgo node 1 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml
  << Timeline
------------------------------
• [FAILED] [3516.199 seconds]
Workload cluster creation Creating a GPU-enabled cluster [OPTIONAL] [It] 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/23 23:34:29 failed trying to get namespace (capz-e2e-1fstlz):namespaces "capz-e2e-1fstlz" not found
  cluster.cluster.x-k8s.io/capz-e2e-1fstlz-gpu serverside-applied
  azurecluster.infrastructure.cluster.x-k8s.io/capz-e2e-1fstlz-gpu serverside-applied
  kubeadmcontrolplane.controlplane.cluster.x-k8s.io/capz-e2e-1fstlz-gpu-control-plane serverside-applied
  azuremachinetemplate.infrastructure.cluster.x-k8s.io/capz-e2e-1fstlz-gpu-control-plane serverside-applied
  azureclusteridentity.infrastructure.cluster.x-k8s.io/cluster-identity-sp serverside-applied
  machinedeployment.cluster.x-k8s.io/capz-e2e-1fstlz-gpu-md-0 serverside-applied
... skipping 2 lines ...
  clusterresourceset.addons.cluster.x-k8s.io/crs-gpu-operator serverside-applied
  configmap/nvidia-clusterpolicy-crd serverside-applied
  configmap/nvidia-gpu-operator-components serverside-applied

  felixconfiguration.crd.projectcalico.org/default configured

  Failed to get logs for Machine capz-e2e-1fstlz-gpu-md-0-66578c8d-9d4cb, Cluster capz-e2e-1fstlz/capz-e2e-1fstlz-gpu: dialing from control plane to target node at capz-e2e-1fstlz-gpu-md-0-kmt9d: ssh: rejected: connect failed (Temporary failure in name resolution)
  << Captured StdOut/StdErr Output

  Timeline >>
  INFO: "" started at Mon, 23 Jan 2023 23:34:28 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-1fstlz" for hosting the cluster @ 01/23/23 23:34:28.946
  Jan 23 23:34:28.946: INFO: starting to create namespace for hosting the "capz-e2e-1fstlz" test spec
... skipping 68 lines ...
  INFO: Waiting for control plane to be ready
  INFO: Waiting for control plane capz-e2e-1fstlz/capz-e2e-1fstlz-gpu-control-plane to be ready (implies underlying nodes to be ready as well)
  STEP: Waiting for the control plane to be ready @ 01/23/23 23:41:51.263
  STEP: Checking all the control plane machines are in the expected failure domains @ 01/23/23 23:41:51.299
  INFO: Waiting for the machine deployments to be provisioned
  STEP: Waiting for the workload nodes to exist @ 01/23/23 23:41:51.409
  [FAILED] in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/machinedeployment_helpers.go:131 @ 01/24/23 00:11:51.411
  Jan 24 00:11:51.411: INFO: FAILED!
  Jan 24 00:11:51.411: INFO: Cleaning up after "Workload cluster creation Creating a GPU-enabled cluster [OPTIONAL] with a single control plane node and 1 node" spec
  STEP: Dumping logs from the "capz-e2e-1fstlz-gpu" workload cluster @ 01/24/23 00:11:51.411
  Jan 24 00:11:51.411: INFO: Dumping workload cluster capz-e2e-1fstlz/capz-e2e-1fstlz-gpu logs
  Jan 24 00:11:51.476: INFO: Collecting logs for Linux node capz-e2e-1fstlz-gpu-control-plane-5mqhh in cluster capz-e2e-1fstlz-gpu in namespace capz-e2e-1fstlz

  Jan 24 00:12:09.914: INFO: Collecting boot logs for AzureMachine capz-e2e-1fstlz-gpu-control-plane-5mqhh
... skipping 61 lines ...
  INFO: Deleting namespace capz-e2e-1fstlz
  Jan 24 00:30:01.475: INFO: Checking if any resources are left over in Azure for spec "create-workload-cluster"
  STEP: Redacting sensitive information from logs @ 01/24/23 00:30:02.095
  INFO: "with a single control plane node and 1 node" started at Tue, 24 Jan 2023 00:33:05 UTC on Ginkgo node 10 of 10 and junit test report to file /logs/artifacts/test_e2e_junit.e2e_suite.1.xml
  << Timeline

  [FAILED] Timed out after 1800.001s.
  Timed out waiting for 1 nodes to be created for MachineDeployment capz-e2e-1fstlz/capz-e2e-1fstlz-gpu-md-0
  Expected
      <int>: 0
  to equal
      <int>: 1
  In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/machinedeployment_helpers.go:131 @ 01/24/23 00:11:51.411
... skipping 23 lines ...
[ReportAfterSuite] PASSED [0.031 seconds]
[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report
autogenerated by Ginkgo
------------------------------

Summarizing 1 Failure:
  [FAIL] Workload cluster creation Creating a GPU-enabled cluster [OPTIONAL] [It] with a single control plane node and 1 node
  /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/machinedeployment_helpers.go:131

Ran 7 of 27 Specs in 3812.638 seconds
FAIL! -- 6 Passed | 1 Failed | 0 Pending | 20 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:429
... skipping 85 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:429

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

--- FAIL: TestE2E (3810.34s)
FAIL


Ginkgo ran 1 suite in 1h7m39.875033482s

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 ...