Recent runs || View in Spyglass
PR | bart0sh: kubelet: prepare DRA resources before CNI setup |
Result | FAILURE |
Tests | 1 failed / 2 succeeded |
Started | |
Elapsed | 58m15s |
Revision | b01a9d005f8b0b6538a7820fef230b1d6e092cab |
Refs |
114364 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\s\[It\]\sConformance\sTests\sconformance\-tests$'
[FAILED] Timed out after 195.014s. Expected success, but got an error: <*errors.withStack | 0xc001f07f98>: { error: <*errors.withMessage | 0xc000784800>{ cause: <*url.Error | 0xc0002be690>{ Op: "Get", URL: "https://capz-conf-q14r4l-5414125b.northeurope.cloudapp.azure.com:6443/version", Err: <*net.OpError | 0xc001a8ebe0>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc00159cf90>{IP: "3\x8a\xb3 ", Port: 6443, Zone: ""}, Err: <*poll.DeadlineExceededError | 0x5d04840>{}, }, }, msg: "Kubernetes cluster unreachable", }, stack: [0x3546ec5, 0x35e9b3b, 0x3642852, 0x154c085, 0x154b57c, 0x196a15a, 0x196b517, 0x196850d, 0x3642009, 0x363278c, 0x36354b7, 0x2fefbf0, 0x3652cc8, 0x19452db, 0x19597f8, 0x14d9741], } Kubernetes cluster unreachable: Get "https://capz-conf-q14r4l-5414125b.northeurope.cloudapp.azure.com:6443/version": dial tcp 51.138.179.32:6443: i/o timeout In [It] at: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:949 @ 02/01/23 18:23:17.992from junit.e2e_suite.1.xml
> Enter [BeforeEach] Conformance Tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:56 @ 02/01/23 18:17:49.984 INFO: Cluster name is capz-conf-q14r4l STEP: Creating namespace "capz-conf-q14r4l" for hosting the cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 02/01/23 18:17:49.984 Feb 1 18:17:49.984: INFO: starting to create namespace for hosting the "capz-conf-q14r4l" test spec INFO: Creating namespace capz-conf-q14r4l INFO: Creating event watcher for namespace "capz-conf-q14r4l" < Exit [BeforeEach] Conformance Tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:56 @ 02/01/23 18:17:50.028 (44ms) > Enter [It] conformance-tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:100 @ 02/01/23 18:17:50.028 conformance-tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:102 @ 02/01/23 18:17:50.028 conformance-tests Name | N | Min | Median | Mean | StdDev | Max INFO: Creating the workload cluster with name "capz-conf-q14r4l" using the "conformance-presubmit-artifacts-windows-containerd" template (Kubernetes v1.27.0-alpha.1.182+b1667918bc8dc4, 1 control-plane machines, 0 worker machines) INFO: Getting the cluster template yaml INFO: clusterctl config cluster capz-conf-q14r4l --infrastructure (default) --kubernetes-version v1.27.0-alpha.1.182+b1667918bc8dc4 --control-plane-machine-count 1 --worker-machine-count 0 --flavor conformance-presubmit-artifacts-windows-containerd INFO: Applying the cluster template yaml to the cluster INFO: Waiting for the cluster infrastructure to be provisioned STEP: Waiting for cluster to enter the provisioned phase - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/cluster_helpers.go:134 @ 02/01/23 18:17:52.85 INFO: Waiting for control plane to be initialized STEP: Installing Calico CNI via helm - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:49 @ 02/01/23 18:20:02.956 STEP: Configuring calico CNI helm chart for IPv4 configuration - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:102 @ 02/01/23 18:20:02.956 [FAILED] Timed out after 195.014s. Expected success, but got an error: <*errors.withStack | 0xc001f07f98>: { error: <*errors.withMessage | 0xc000784800>{ cause: <*url.Error | 0xc0002be690>{ Op: "Get", URL: "https://capz-conf-q14r4l-5414125b.northeurope.cloudapp.azure.com:6443/version", Err: <*net.OpError | 0xc001a8ebe0>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc00159cf90>{IP: "3\x8a\xb3 ", Port: 6443, Zone: ""}, Err: <*poll.DeadlineExceededError | 0x5d04840>{}, }, }, msg: "Kubernetes cluster unreachable", }, stack: [0x3546ec5, 0x35e9b3b, 0x3642852, 0x154c085, 0x154b57c, 0x196a15a, 0x196b517, 0x196850d, 0x3642009, 0x363278c, 0x36354b7, 0x2fefbf0, 0x3652cc8, 0x19452db, 0x19597f8, 0x14d9741], } Kubernetes cluster unreachable: Get "https://capz-conf-q14r4l-5414125b.northeurope.cloudapp.azure.com:6443/version": dial tcp 51.138.179.32:6443: i/o timeout In [It] at: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:949 @ 02/01/23 18:23:17.992 < Exit [It] conformance-tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:100 @ 02/01/23 18:23:17.992 (5m27.964s) > Enter [AfterEach] Conformance Tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:242 @ 02/01/23 18:23:17.992 Feb 1 18:23:17.992: INFO: FAILED! Feb 1 18:23:17.992: INFO: Cleaning up after "Conformance Tests conformance-tests" spec STEP: Dumping logs from the "capz-conf-q14r4l" workload cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 02/01/23 18:23:17.992 Feb 1 18:23:17.992: INFO: Dumping workload cluster capz-conf-q14r4l/capz-conf-q14r4l logs Feb 1 18:23:18.035: INFO: Collecting logs for Linux node capz-conf-q14r4l-control-plane-gd6m2 in cluster capz-conf-q14r4l in namespace capz-conf-q14r4l Feb 1 18:23:33.626: INFO: Collecting boot logs for AzureMachine capz-conf-q14r4l-control-plane-gd6m2 Feb 1 18:23:35.499: INFO: Unable to collect logs as node doesn't have addresses Feb 1 18:23:35.499: INFO: Collecting logs for Windows node capz-conf-q14r4l-md-win-ldfrg in cluster capz-conf-q14r4l in namespace capz-conf-q14r4l Feb 1 18:27:51.990: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-q14r4l-md-win-ldfrg to /logs/artifacts/clusters/capz-conf-q14r4l/machines/capz-conf-q14r4l-md-win-79d777f5f7-cf8ng/crashdumps.tar Feb 1 18:27:53.527: INFO: Collecting boot logs for AzureMachine capz-conf-q14r4l-md-win-ldfrg Feb 1 18:27:53.577: INFO: Unable to collect logs as node doesn't have addresses Feb 1 18:27:53.577: INFO: Collecting logs for Windows node capz-conf-q14r4l-md-win-vxrdt in cluster capz-conf-q14r4l in namespace capz-conf-q14r4l Feb 1 18:32:13.889: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-q14r4l-md-win-vxrdt to /logs/artifacts/clusters/capz-conf-q14r4l/machines/capz-conf-q14r4l-md-win-79d777f5f7-hbscq/crashdumps.tar Feb 1 18:32:14.985: INFO: Collecting boot logs for AzureMachine capz-conf-q14r4l-md-win-vxrdt Feb 1 18:32:16.314: INFO: Dumping workload cluster capz-conf-q14r4l/capz-conf-q14r4l kube-system pod logs Feb 1 18:32:17.800: INFO: Creating log watcher for controller kube-system/containerd-logger-bqx6c, container containerd-logger Feb 1 18:32:17.800: INFO: Describing Pod kube-system/containerd-logger-bqx6c Feb 1 18:32:18.016: INFO: Creating log watcher for controller kube-system/containerd-logger-nlrcm, container containerd-logger Feb 1 18:32:18.016: INFO: Describing Pod kube-system/containerd-logger-nlrcm Feb 1 18:32:18.232: INFO: Creating log watcher for controller kube-system/coredns-56f4c55bf9-vwtbq, container coredns Feb 1 18:32:18.232: INFO: Describing Pod kube-system/coredns-56f4c55bf9-vwtbq Feb 1 18:32:18.448: INFO: Creating log watcher for controller kube-system/coredns-56f4c55bf9-zh289, container coredns Feb 1 18:32:18.449: INFO: Describing Pod kube-system/coredns-56f4c55bf9-zh289 Feb 1 18:32:18.661: INFO: Creating log watcher for controller kube-system/etcd-capz-conf-q14r4l-control-plane-gd6m2, container etcd Feb 1 18:32:18.661: INFO: Describing Pod kube-system/etcd-capz-conf-q14r4l-control-plane-gd6m2 Feb 1 18:32:18.879: INFO: Creating log watcher for controller kube-system/kube-apiserver-capz-conf-q14r4l-control-plane-gd6m2, container kube-apiserver Feb 1 18:32:18.880: INFO: Describing Pod kube-system/kube-apiserver-capz-conf-q14r4l-control-plane-gd6m2 Feb 1 18:32:19.091: INFO: Creating log watcher for controller kube-system/kube-controller-manager-capz-conf-q14r4l-control-plane-gd6m2, container kube-controller-manager Feb 1 18:32:19.091: INFO: Describing Pod kube-system/kube-controller-manager-capz-conf-q14r4l-control-plane-gd6m2 Feb 1 18:32:19.437: INFO: Creating log watcher for controller kube-system/kube-proxy-g2d5v, container kube-proxy Feb 1 18:32:19.437: INFO: Describing Pod kube-system/kube-proxy-g2d5v Feb 1 18:32:19.644: INFO: Creating log watcher for controller kube-system/kube-proxy-windows-27zcj, container kube-proxy Feb 1 18:32:19.644: INFO: Describing Pod kube-system/kube-proxy-windows-27zcj Feb 1 18:32:19.851: INFO: Creating log watcher for controller kube-system/kube-proxy-windows-c57d8, container kube-proxy Feb 1 18:32:19.852: INFO: Describing Pod kube-system/kube-proxy-windows-c57d8 Feb 1 18:32:20.089: INFO: Creating log watcher for controller kube-system/kube-scheduler-capz-conf-q14r4l-control-plane-gd6m2, container kube-scheduler Feb 1 18:32:20.089: INFO: Describing Pod kube-system/kube-scheduler-capz-conf-q14r4l-control-plane-gd6m2 Feb 1 18:32:20.485: INFO: Fetching kube-system pod logs took 4.1708539s Feb 1 18:32:20.486: INFO: Dumping workload cluster capz-conf-q14r4l/capz-conf-q14r4l Azure activity log Feb 1 18:32:20.485: INFO: Creating log watcher for controller kube-system/metrics-server-c9574f845-zx7rb, container metrics-server Feb 1 18:32:20.485: INFO: Describing Pod kube-system/metrics-server-c9574f845-zx7rb Feb 1 18:32:22.848: INFO: Fetching activity logs took 2.362705282s Feb 1 18:32:22.848: INFO: Dumping all the Cluster API resources in the "capz-conf-q14r4l" namespace Feb 1 18:32:23.220: INFO: Deleting all clusters in the capz-conf-q14r4l namespace STEP: Deleting cluster capz-conf-q14r4l - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/ginkgoextensions/output.go:35 @ 02/01/23 18:32:23.236 INFO: Waiting for the Cluster capz-conf-q14r4l/capz-conf-q14r4l to be deleted STEP: Waiting for cluster capz-conf-q14r4l to be deleted - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/ginkgoextensions/output.go:35 @ 02/01/23 18:32:23.25 Feb 1 18:40:13.576: INFO: Deleting namespace used for hosting the "conformance-tests" test spec INFO: Deleting namespace capz-conf-q14r4l Feb 1 18:40:13.610: INFO: Checking if any resources are left over in Azure for spec "conformance-tests" STEP: Redacting sensitive information from logs - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:216 @ 02/01/23 18:40:14.266 < Exit [AfterEach] Conformance Tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:242 @ 02/01/23 18:40:26.36 (17m8.369s)
Filter through log files | View test history on testgrid
capz-e2e [SynchronizedAfterSuite]
capz-e2e [SynchronizedBeforeSuite]
capz-e2e [It] Running the Cluster API E2E tests API Version Upgrade upgrade from v1alpha4 to v1beta1, and scale workload clusters created in v1alpha4 Should create a management cluster and then upgrade all the providers
capz-e2e [It] Running the Cluster API E2E tests Running KCP upgrade in a HA cluster [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e [It] Running the Cluster API E2E tests Running KCP upgrade in a HA cluster using scale in rollout [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e [It] Running the Cluster API E2E tests Running the MachineDeployment rollout spec Should successfully upgrade Machines upon changes in relevant MachineDeployment fields
capz-e2e [It] Running the Cluster API E2E tests Running the quick-start spec Should create a workload cluster
capz-e2e [It] Running the Cluster API E2E tests Running the self-hosted spec Should pivot the bootstrap cluster to a self-hosted cluster
capz-e2e [It] Running the Cluster API E2E tests Running the workload cluster upgrade spec [K8s-Upgrade] Should create and upgrade a workload cluster and eventually run kubetest
capz-e2e [It] Running the Cluster API E2E tests Should successfully exercise machine pools Should successfully create a cluster with machine pool machines
capz-e2e [It] Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger KCP remediation
capz-e2e [It] Running the Cluster API E2E tests Should successfully remediate unhealthy machines with MachineHealthCheck Should successfully trigger machine deployment remediation
capz-e2e [It] Running the Cluster API E2E tests Should successfully scale out and scale in a MachineDeployment Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count
capz-e2e [It] Running the Cluster API E2E tests Should successfully set and use node drain timeout A node should be forcefully removed if it cannot be drained in time
capz-e2e [It] Workload cluster creation Creating a Flatcar cluster [OPTIONAL] With Flatcar control-plane and worker nodes
capz-e2e [It] Workload cluster creation Creating a GPU-enabled cluster [OPTIONAL] with a single control plane node and 1 node
capz-e2e [It] Workload cluster creation Creating a VMSS cluster [REQUIRED] with a single control plane node and an AzureMachinePool with 2 Linux and 2 Windows worker nodes
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
capz-e2e [It] Workload cluster creation Creating a cluster that uses the external cloud provider and machinepools [OPTIONAL] with 1 control plane node and 1 machinepool
capz-e2e [It] Workload cluster creation Creating a dual-stack cluster [OPTIONAL] With dual-stack worker node
capz-e2e [It] Workload cluster creation Creating a highly available cluster [REQUIRED] With 3 control-plane nodes and 2 Linux and 2 Windows worker nodes
capz-e2e [It] Workload cluster creation Creating a ipv6 control-plane cluster [REQUIRED] With ipv6 worker node
capz-e2e [It] Workload cluster creation Creating a private cluster [OPTIONAL] Creates a public management cluster in a custom vnet
capz-e2e [It] Workload cluster creation Creating an AKS cluster [Managed Kubernetes] with a single control plane node and 1 node
capz-e2e [It] Workload cluster creation Creating clusters using clusterclass [OPTIONAL] with a single control plane node, one linux worker node, and one windows worker node
... skipping 137 lines ... Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 138 100 138 0 0 3285 0 --:--:-- --:--:-- --:--:-- 3285 100 34 100 34 0 0 343 0 --:--:-- --:--:-- --:--:-- 343 using CI_VERSION=v1.27.0-alpha.1.182+b1667918bc8dc4 using KUBERNETES_VERSION=v1.27.0-alpha.1.182+b1667918bc8dc4 using IMAGE_TAG=v1.27.0-alpha.1.187_537346c29aabc1 Error response from daemon: manifest for capzci.azurecr.io/kube-apiserver:v1.27.0-alpha.1.187_537346c29aabc1 not found: manifest unknown: manifest tagged by "v1.27.0-alpha.1.187_537346c29aabc1" is not found Building Kubernetes make: Entering directory '/home/prow/go/src/k8s.io/kubernetes' +++ [0201 17:43:44] Verifying Prerequisites.... +++ [0201 17:43:44] Building Docker image kube-build:build-3e847347a1-5-v1.26.0-go1.19.5-bullseye.0 +++ [0201 17:46:52] Creating data container kube-build-data-3e847347a1-5-v1.26.0-go1.19.5-bullseye.0 +++ [0201 17:47:13] Syncing sources to container ... skipping 767 lines ... [38;5;243m------------------------------[0m [0mConformance Tests [0m[1mconformance-tests[0m [38;5;243m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:100[0m INFO: Cluster name is capz-conf-q14r4l [1mSTEP:[0m Creating namespace "capz-conf-q14r4l" for hosting the cluster [38;5;243m@ 02/01/23 18:17:49.984[0m Feb 1 18:17:49.984: INFO: starting to create namespace for hosting the "capz-conf-q14r4l" test spec 2023/02/01 18:17:49 failed trying to get namespace (capz-conf-q14r4l):namespaces "capz-conf-q14r4l" not found INFO: Creating namespace capz-conf-q14r4l INFO: Creating event watcher for namespace "capz-conf-q14r4l" [1mconformance-tests[38;5;243m - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:102 @ 02/01/23 18:17:50.028[0m [1mconformance-tests [0m[1mName[0m | [1mN[0m | [1mMin[0m | [1mMedian[0m | [1mMean[0m | [1mStdDev[0m | [1mMax[0m INFO: Creating the workload cluster with name "capz-conf-q14r4l" using the "conformance-presubmit-artifacts-windows-containerd" template (Kubernetes v1.27.0-alpha.1.182+b1667918bc8dc4, 1 control-plane machines, 0 worker machines) ... skipping 23 lines ... INFO: Waiting for the cluster infrastructure to be provisioned [1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 02/01/23 18:17:52.85[0m INFO: Waiting for control plane to be initialized [1mSTEP:[0m Installing Calico CNI via helm [38;5;243m@ 02/01/23 18:20:02.956[0m [1mSTEP:[0m Configuring calico CNI helm chart for IPv4 configuration [38;5;243m@ 02/01/23 18:20:02.956[0m [38;5;9m[FAILED][0m in [It] - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:949 [38;5;243m@ 02/01/23 18:23:17.992[0m Feb 1 18:23:17.992: INFO: FAILED! Feb 1 18:23:17.992: INFO: Cleaning up after "Conformance Tests conformance-tests" spec [1mSTEP:[0m Dumping logs from the "capz-conf-q14r4l" workload cluster [38;5;243m@ 02/01/23 18:23:17.992[0m Feb 1 18:23:17.992: INFO: Dumping workload cluster capz-conf-q14r4l/capz-conf-q14r4l logs Feb 1 18:23:18.035: INFO: Collecting logs for Linux node capz-conf-q14r4l-control-plane-gd6m2 in cluster capz-conf-q14r4l in namespace capz-conf-q14r4l Feb 1 18:23:33.626: INFO: Collecting boot logs for AzureMachine capz-conf-q14r4l-control-plane-gd6m2 Feb 1 18:23:35.499: INFO: Unable to collect logs as node doesn't have addresses Feb 1 18:23:35.499: INFO: Collecting logs for Windows node capz-conf-q14r4l-md-win-ldfrg in cluster capz-conf-q14r4l in namespace capz-conf-q14r4l Feb 1 18:27:51.990: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-q14r4l-md-win-ldfrg to /logs/artifacts/clusters/capz-conf-q14r4l/machines/capz-conf-q14r4l-md-win-79d777f5f7-cf8ng/crashdumps.tar Feb 1 18:27:53.527: INFO: Collecting boot logs for AzureMachine capz-conf-q14r4l-md-win-ldfrg Failed to get logs for Machine capz-conf-q14r4l-md-win-79d777f5f7-cf8ng, Cluster capz-conf-q14r4l/capz-conf-q14r4l: [dialing from control plane to target node at capz-conf-q14r4l-md-win-ldfrg: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil] Feb 1 18:27:53.577: INFO: Unable to collect logs as node doesn't have addresses Feb 1 18:27:53.577: INFO: Collecting logs for Windows node capz-conf-q14r4l-md-win-vxrdt in cluster capz-conf-q14r4l in namespace capz-conf-q14r4l Feb 1 18:32:13.889: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-q14r4l-md-win-vxrdt to /logs/artifacts/clusters/capz-conf-q14r4l/machines/capz-conf-q14r4l-md-win-79d777f5f7-hbscq/crashdumps.tar Feb 1 18:32:14.985: INFO: Collecting boot logs for AzureMachine capz-conf-q14r4l-md-win-vxrdt Failed to get logs for Machine capz-conf-q14r4l-md-win-79d777f5f7-hbscq, Cluster capz-conf-q14r4l/capz-conf-q14r4l: dialing from control plane to target node at capz-conf-q14r4l-md-win-vxrdt: ssh: rejected: connect failed (Temporary failure in name resolution) Feb 1 18:32:16.314: INFO: Dumping workload cluster capz-conf-q14r4l/capz-conf-q14r4l kube-system pod logs Feb 1 18:32:17.800: INFO: Creating log watcher for controller kube-system/containerd-logger-bqx6c, container containerd-logger Feb 1 18:32:17.800: INFO: Describing Pod kube-system/containerd-logger-bqx6c Feb 1 18:32:18.016: INFO: Creating log watcher for controller kube-system/containerd-logger-nlrcm, container containerd-logger Feb 1 18:32:18.016: INFO: Describing Pod kube-system/containerd-logger-nlrcm Feb 1 18:32:18.232: INFO: Creating log watcher for controller kube-system/coredns-56f4c55bf9-vwtbq, container coredns ... skipping 25 lines ... INFO: Waiting for the Cluster capz-conf-q14r4l/capz-conf-q14r4l to be deleted [1mSTEP:[0m Waiting for cluster capz-conf-q14r4l to be deleted [38;5;243m@ 02/01/23 18:32:23.25[0m Feb 1 18:40:13.576: INFO: Deleting namespace used for hosting the "conformance-tests" test spec INFO: Deleting namespace capz-conf-q14r4l Feb 1 18:40:13.610: INFO: Checking if any resources are left over in Azure for spec "conformance-tests" [1mSTEP:[0m Redacting sensitive information from logs [38;5;243m@ 02/01/23 18:40:14.266[0m [38;5;9m• [FAILED] [1356.377 seconds][0m [0mConformance Tests [38;5;9m[1m[It] conformance-tests[0m [38;5;243m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:100[0m [38;5;9m[FAILED] Timed out after 195.014s. Expected success, but got an error: <*errors.withStack | 0xc001f07f98>: { error: <*errors.withMessage | 0xc000784800>{ cause: <*url.Error | 0xc0002be690>{ Op: "Get", URL: "https://capz-conf-q14r4l-5414125b.northeurope.cloudapp.azure.com:6443/version", Err: <*net.OpError | 0xc001a8ebe0>{ Op: "dial", Net: "tcp", Source: nil, ... skipping 30 lines ... [0m[1m[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report[0m [38;5;243mautogenerated by Ginkgo[0m [38;5;10m[ReportAfterSuite] PASSED [0.004 seconds][0m [38;5;243m------------------------------[0m [38;5;9m[1mSummarizing 1 Failure:[0m [38;5;9m[FAIL][0m [0mConformance Tests [38;5;9m[1m[It] conformance-tests[0m [38;5;243m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:949[0m [38;5;9m[1mRan 1 of 24 Specs in 1527.557 seconds[0m [38;5;9m[1mFAIL![0m -- [38;5;10m[1m0 Passed[0m | [38;5;9m[1m1 Failed[0m | [38;5;11m[1m0 Pending[0m | [38;5;14m[1m23 Skipped[0m [38;5;228mYou're using deprecated Ginkgo functionality:[0m [38;5;228m=============================================[0m [38;5;11mCurrentGinkgoTestDescription() is deprecated in Ginkgo V2. Use CurrentSpecReport() instead.[0m [1mLearn more at:[0m [38;5;14m[4mhttps://onsi.github.io/ginkgo/MIGRATING_TO_V2#changed-currentginkgotestdescription[0m [38;5;243m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:282[0m [38;5;243m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:285[0m [38;5;243mTo silence deprecations that can be silenced set the following environment variable:[0m [38;5;243mACK_GINKGO_DEPRECATIONS=2.7.1[0m --- FAIL: TestE2E (1527.57s) FAIL Ginkgo ran 1 suite in 29m10.456898331s Test Suite Failed make[3]: *** [Makefile:654: test-e2e-run] Error 1 make[3]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' make[2]: *** [Makefile:669: test-e2e-skip-push] Error 2 make[2]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' make[1]: *** [Makefile:685: test-conformance] Error 2 make[1]: Leaving directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure' make: *** [Makefile:695: test-windows-upstream] Error 2 ================ REDACTING LOGS ================ All sensitive variables are redacted + EXIT_VALUE=2 + set +o xtrace Cleaning up after docker in docker. ================================================================================ ... skipping 7 lines ...