Recent runs || View in Spyglass
PR | danwinship: Move GetHostname() from k/k/pkg/util/node to k/component-helpers/node/util |
Result | FAILURE |
Tests | 1 failed / 2 succeeded |
Started | |
Elapsed | 59m21s |
Revision | f994ae2521f9a9c7cdb3646225b560db49637434 |
Refs |
115338 |
go run hack/e2e.go -v --test --test_args='--ginkgo.focus=capz\-e2e\s\[It\]\sConformance\sTests\sconformance\-tests$'
[FAILED] Timed out after 180.001s. Expected success, but got an error: <*errors.withStack | 0xc00109f950>: { error: <*errors.withMessage | 0xc00068e3c0>{ cause: <*url.Error | 0xc002a97ce0>{ Op: "Get", URL: "https://capz-conf-yrbcrl-6e411607.uksouth.cloudapp.azure.com:6443/version", Err: <*net.OpError | 0xc0012a0af0>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc001fbcc30>{IP: [51, 11, 29, 22], Port: 6443, Zone: ""}, Err: <*os.SyscallError | 0xc00068e300>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, }, msg: "Kubernetes cluster unreachable", }, stack: [0x3547885, 0x35ea4fb, 0x36428b2, 0x154d085, 0x154c57c, 0x196b29a, 0x196c657, 0x196964d, 0x3642149, 0x3632654, 0x3635637, 0x2ff0810, 0x3652cc8, 0x194637b, 0x195a958, 0x14da741], } Kubernetes cluster unreachable: Get "https://capz-conf-yrbcrl-6e411607.uksouth.cloudapp.azure.com:6443/version": dial tcp 51.11.29.22:6443: connect: connection refused In [It] at: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:949 @ 01/28/23 00:09:07.629from 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 @ 01/28/23 00:03:44.08 INFO: Cluster name is capz-conf-yrbcrl STEP: Creating namespace "capz-conf-yrbcrl" for hosting the cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/28/23 00:03:44.08 Jan 28 00:03:44.080: INFO: starting to create namespace for hosting the "capz-conf-yrbcrl" test spec INFO: Creating namespace capz-conf-yrbcrl INFO: Creating event watcher for namespace "capz-conf-yrbcrl" < Exit [BeforeEach] Conformance Tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:56 @ 01/28/23 00:03:44.137 (57ms) > Enter [It] conformance-tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:100 @ 01/28/23 00:03:44.137 conformance-tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:102 @ 01/28/23 00:03:44.137 conformance-tests Name | N | Min | Median | Mean | StdDev | Max INFO: Creating the workload cluster with name "capz-conf-yrbcrl" using the "conformance-presubmit-artifacts-windows-containerd" template (Kubernetes v1.27.0-alpha.1.61+1f02f43ec6910c, 1 control-plane machines, 0 worker machines) INFO: Getting the cluster template yaml INFO: clusterctl config cluster capz-conf-yrbcrl --infrastructure (default) --kubernetes-version v1.27.0-alpha.1.61+1f02f43ec6910c --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 @ 01/28/23 00:03:47.471 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:51 @ 01/28/23 00:06:07.609 STEP: Configuring calico CNI helm chart for IPv4 configuration - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/cni.go:112 @ 01/28/23 00:06:07.609 [FAILED] Timed out after 180.001s. Expected success, but got an error: <*errors.withStack | 0xc00109f950>: { error: <*errors.withMessage | 0xc00068e3c0>{ cause: <*url.Error | 0xc002a97ce0>{ Op: "Get", URL: "https://capz-conf-yrbcrl-6e411607.uksouth.cloudapp.azure.com:6443/version", Err: <*net.OpError | 0xc0012a0af0>{ Op: "dial", Net: "tcp", Source: nil, Addr: <*net.TCPAddr | 0xc001fbcc30>{IP: [51, 11, 29, 22], Port: 6443, Zone: ""}, Err: <*os.SyscallError | 0xc00068e300>{ Syscall: "connect", Err: <syscall.Errno>0x6f, }, }, }, msg: "Kubernetes cluster unreachable", }, stack: [0x3547885, 0x35ea4fb, 0x36428b2, 0x154d085, 0x154c57c, 0x196b29a, 0x196c657, 0x196964d, 0x3642149, 0x3632654, 0x3635637, 0x2ff0810, 0x3652cc8, 0x194637b, 0x195a958, 0x14da741], } Kubernetes cluster unreachable: Get "https://capz-conf-yrbcrl-6e411607.uksouth.cloudapp.azure.com:6443/version": dial tcp 51.11.29.22:6443: connect: connection refused In [It] at: /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/helpers.go:949 @ 01/28/23 00:09:07.629 < Exit [It] conformance-tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:100 @ 01/28/23 00:09:07.63 (5m23.493s) > Enter [AfterEach] Conformance Tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:242 @ 01/28/23 00:09:07.63 Jan 28 00:09:07.630: INFO: FAILED! Jan 28 00:09:07.630: INFO: Cleaning up after "Conformance Tests conformance-tests" spec STEP: Dumping logs from the "capz-conf-yrbcrl" workload cluster - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/common.go:92 @ 01/28/23 00:09:07.63 Jan 28 00:09:07.630: INFO: Dumping workload cluster capz-conf-yrbcrl/capz-conf-yrbcrl logs Jan 28 00:09:07.699: INFO: Collecting logs for Linux node capz-conf-yrbcrl-control-plane-b9jbl in cluster capz-conf-yrbcrl in namespace capz-conf-yrbcrl Jan 28 00:09:18.732: INFO: Collecting boot logs for AzureMachine capz-conf-yrbcrl-control-plane-b9jbl Jan 28 00:09:20.195: INFO: Unable to collect logs as node doesn't have addresses Jan 28 00:09:20.195: INFO: Collecting logs for Windows node capz-conf-yrbcrl-md-win-6j6r2 in cluster capz-conf-yrbcrl in namespace capz-conf-yrbcrl Jan 28 00:13:41.284: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-yrbcrl-md-win-6j6r2 to /logs/artifacts/clusters/capz-conf-yrbcrl/machines/capz-conf-yrbcrl-md-win-5494d99f98-6c827/crashdumps.tar Jan 28 00:13:42.972: INFO: Collecting boot logs for AzureMachine capz-conf-yrbcrl-md-win-6j6r2 Jan 28 00:13:43.008: INFO: Unable to collect logs as node doesn't have addresses Jan 28 00:13:43.008: INFO: Collecting logs for Windows node capz-conf-yrbcrl-md-win-l87l9 in cluster capz-conf-yrbcrl in namespace capz-conf-yrbcrl Jan 28 00:18:05.556: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-yrbcrl-md-win-l87l9 to /logs/artifacts/clusters/capz-conf-yrbcrl/machines/capz-conf-yrbcrl-md-win-5494d99f98-g8cxg/crashdumps.tar Jan 28 00:18:07.460: INFO: Collecting boot logs for AzureMachine capz-conf-yrbcrl-md-win-l87l9 Jan 28 00:18:08.880: INFO: Dumping workload cluster capz-conf-yrbcrl/capz-conf-yrbcrl kube-system pod logs Jan 28 00:18:10.377: INFO: Creating log watcher for controller kube-system/containerd-logger-4mtpc, container containerd-logger Jan 28 00:18:10.377: INFO: Describing Pod kube-system/containerd-logger-4mtpc Jan 28 00:18:10.594: INFO: Creating log watcher for controller kube-system/containerd-logger-w7728, container containerd-logger Jan 28 00:18:10.594: INFO: Describing Pod kube-system/containerd-logger-w7728 Jan 28 00:18:10.812: INFO: Creating log watcher for controller kube-system/coredns-56f4c55bf9-jkbcd, container coredns Jan 28 00:18:10.812: INFO: Describing Pod kube-system/coredns-56f4c55bf9-jkbcd Jan 28 00:18:11.030: INFO: Describing Pod kube-system/coredns-56f4c55bf9-wkfsp Jan 28 00:18:11.030: INFO: Creating log watcher for controller kube-system/coredns-56f4c55bf9-wkfsp, container coredns Jan 28 00:18:11.248: INFO: Creating log watcher for controller kube-system/etcd-capz-conf-yrbcrl-control-plane-b9jbl, container etcd Jan 28 00:18:11.248: INFO: Describing Pod kube-system/etcd-capz-conf-yrbcrl-control-plane-b9jbl Jan 28 00:18:11.472: INFO: Creating log watcher for controller kube-system/kube-apiserver-capz-conf-yrbcrl-control-plane-b9jbl, container kube-apiserver Jan 28 00:18:11.472: INFO: Describing Pod kube-system/kube-apiserver-capz-conf-yrbcrl-control-plane-b9jbl Jan 28 00:18:11.684: INFO: Creating log watcher for controller kube-system/kube-controller-manager-capz-conf-yrbcrl-control-plane-b9jbl, container kube-controller-manager Jan 28 00:18:11.685: INFO: Describing Pod kube-system/kube-controller-manager-capz-conf-yrbcrl-control-plane-b9jbl Jan 28 00:18:12.023: INFO: Creating log watcher for controller kube-system/kube-proxy-windows-xwk9r, container kube-proxy Jan 28 00:18:12.023: INFO: Describing Pod kube-system/kube-proxy-windows-xwk9r Jan 28 00:18:12.231: INFO: Creating log watcher for controller kube-system/kube-proxy-windows-zbcbs, container kube-proxy Jan 28 00:18:12.232: INFO: Describing Pod kube-system/kube-proxy-windows-zbcbs Jan 28 00:18:12.440: INFO: Creating log watcher for controller kube-system/kube-proxy-xcbkp, container kube-proxy Jan 28 00:18:12.440: INFO: Describing Pod kube-system/kube-proxy-xcbkp Jan 28 00:18:12.663: INFO: Describing Pod kube-system/kube-scheduler-capz-conf-yrbcrl-control-plane-b9jbl Jan 28 00:18:12.663: INFO: Creating log watcher for controller kube-system/kube-scheduler-capz-conf-yrbcrl-control-plane-b9jbl, container kube-scheduler Jan 28 00:18:13.063: INFO: Fetching kube-system pod logs took 4.183293154s Jan 28 00:18:13.063: INFO: Dumping workload cluster capz-conf-yrbcrl/capz-conf-yrbcrl Azure activity log Jan 28 00:18:13.063: INFO: Creating log watcher for controller kube-system/metrics-server-c9574f845-fg6s6, container metrics-server Jan 28 00:18:13.063: INFO: Describing Pod kube-system/metrics-server-c9574f845-fg6s6 Jan 28 00:18:15.110: INFO: Fetching activity logs took 2.04691019s Jan 28 00:18:15.110: INFO: Dumping all the Cluster API resources in the "capz-conf-yrbcrl" namespace Jan 28 00:18:15.531: INFO: Deleting all clusters in the capz-conf-yrbcrl namespace STEP: Deleting cluster capz-conf-yrbcrl - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/ginkgoextensions/output.go:35 @ 01/28/23 00:18:15.551 INFO: Waiting for the Cluster capz-conf-yrbcrl/capz-conf-yrbcrl to be deleted STEP: Waiting for cluster capz-conf-yrbcrl to be deleted - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.2/framework/ginkgoextensions/output.go:35 @ 01/28/23 00:18:15.567 Jan 28 00:26:05.927: INFO: Deleting namespace used for hosting the "conformance-tests" test spec INFO: Deleting namespace capz-conf-yrbcrl Jan 28 00:26:05.961: 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 @ 01/28/23 00:26:06.497 < Exit [AfterEach] Conformance Tests - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:242 @ 01/28/23 00:26:18.011 (17m10.381s)
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 4058 0 --:--:-- --:--:-- --:--:-- 4058 100 33 100 33 0 0 314 0 --:--:-- --:--:-- --:--:-- 314 using CI_VERSION=v1.27.0-alpha.1.61+1f02f43ec6910c using KUBERNETES_VERSION=v1.27.0-alpha.1.61+1f02f43ec6910c using IMAGE_TAG=v1.27.0-alpha.1.65_660952b5c0f998 Error response from daemon: manifest for capzci.azurecr.io/kube-apiserver:v1.27.0-alpha.1.65_660952b5c0f998 not found: manifest unknown: manifest tagged by "v1.27.0-alpha.1.65_660952b5c0f998" is not found Building Kubernetes make: Entering directory '/home/prow/go/src/k8s.io/kubernetes' +++ [0127 23:28:30] Verifying Prerequisites.... +++ [0127 23:28:30] Building Docker image kube-build:build-1289b2feb8-5-v1.26.0-go1.19.5-bullseye.0 +++ [0127 23:31:45] Creating data container kube-build-data-1289b2feb8-5-v1.26.0-go1.19.5-bullseye.0 +++ [0127 23:32:06] Syncing sources to container ... skipping 766 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-yrbcrl [1mSTEP:[0m Creating namespace "capz-conf-yrbcrl" for hosting the cluster [38;5;243m@ 01/28/23 00:03:44.08[0m Jan 28 00:03:44.080: INFO: starting to create namespace for hosting the "capz-conf-yrbcrl" test spec 2023/01/28 00:03:44 failed trying to get namespace (capz-conf-yrbcrl):namespaces "capz-conf-yrbcrl" not found INFO: Creating namespace capz-conf-yrbcrl INFO: Creating event watcher for namespace "capz-conf-yrbcrl" [1mconformance-tests[38;5;243m - /home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/conformance_test.go:102 @ 01/28/23 00:03:44.137[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-yrbcrl" using the "conformance-presubmit-artifacts-windows-containerd" template (Kubernetes v1.27.0-alpha.1.61+1f02f43ec6910c, 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@ 01/28/23 00:03:47.471[0m INFO: Waiting for control plane to be initialized [1mSTEP:[0m Installing Calico CNI via helm [38;5;243m@ 01/28/23 00:06:07.609[0m [1mSTEP:[0m Configuring calico CNI helm chart for IPv4 configuration [38;5;243m@ 01/28/23 00:06:07.609[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@ 01/28/23 00:09:07.629[0m Jan 28 00:09:07.630: INFO: FAILED! Jan 28 00:09:07.630: INFO: Cleaning up after "Conformance Tests conformance-tests" spec [1mSTEP:[0m Dumping logs from the "capz-conf-yrbcrl" workload cluster [38;5;243m@ 01/28/23 00:09:07.63[0m Jan 28 00:09:07.630: INFO: Dumping workload cluster capz-conf-yrbcrl/capz-conf-yrbcrl logs Jan 28 00:09:07.699: INFO: Collecting logs for Linux node capz-conf-yrbcrl-control-plane-b9jbl in cluster capz-conf-yrbcrl in namespace capz-conf-yrbcrl Jan 28 00:09:18.732: INFO: Collecting boot logs for AzureMachine capz-conf-yrbcrl-control-plane-b9jbl Jan 28 00:09:20.195: INFO: Unable to collect logs as node doesn't have addresses Jan 28 00:09:20.195: INFO: Collecting logs for Windows node capz-conf-yrbcrl-md-win-6j6r2 in cluster capz-conf-yrbcrl in namespace capz-conf-yrbcrl Jan 28 00:13:41.284: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-yrbcrl-md-win-6j6r2 to /logs/artifacts/clusters/capz-conf-yrbcrl/machines/capz-conf-yrbcrl-md-win-5494d99f98-6c827/crashdumps.tar Jan 28 00:13:42.972: INFO: Collecting boot logs for AzureMachine capz-conf-yrbcrl-md-win-6j6r2 Failed to get logs for Machine capz-conf-yrbcrl-md-win-5494d99f98-6c827, Cluster capz-conf-yrbcrl/capz-conf-yrbcrl: [dialing from control plane to target node at capz-conf-yrbcrl-md-win-6j6r2: ssh: rejected: connect failed (Temporary failure in name resolution), Unable to collect VM Boot Diagnostic logs: AzureMachine provider ID is nil] Jan 28 00:13:43.008: INFO: Unable to collect logs as node doesn't have addresses Jan 28 00:13:43.008: INFO: Collecting logs for Windows node capz-conf-yrbcrl-md-win-l87l9 in cluster capz-conf-yrbcrl in namespace capz-conf-yrbcrl Jan 28 00:18:05.556: INFO: Attempting to copy file /c:/crashdumps.tar on node capz-conf-yrbcrl-md-win-l87l9 to /logs/artifacts/clusters/capz-conf-yrbcrl/machines/capz-conf-yrbcrl-md-win-5494d99f98-g8cxg/crashdumps.tar Jan 28 00:18:07.460: INFO: Collecting boot logs for AzureMachine capz-conf-yrbcrl-md-win-l87l9 Failed to get logs for Machine capz-conf-yrbcrl-md-win-5494d99f98-g8cxg, Cluster capz-conf-yrbcrl/capz-conf-yrbcrl: dialing from control plane to target node at capz-conf-yrbcrl-md-win-l87l9: ssh: rejected: connect failed (Temporary failure in name resolution) Jan 28 00:18:08.880: INFO: Dumping workload cluster capz-conf-yrbcrl/capz-conf-yrbcrl kube-system pod logs Jan 28 00:18:10.377: INFO: Creating log watcher for controller kube-system/containerd-logger-4mtpc, container containerd-logger Jan 28 00:18:10.377: INFO: Describing Pod kube-system/containerd-logger-4mtpc Jan 28 00:18:10.594: INFO: Creating log watcher for controller kube-system/containerd-logger-w7728, container containerd-logger Jan 28 00:18:10.594: INFO: Describing Pod kube-system/containerd-logger-w7728 Jan 28 00:18:10.812: INFO: Creating log watcher for controller kube-system/coredns-56f4c55bf9-jkbcd, container coredns ... skipping 25 lines ... INFO: Waiting for the Cluster capz-conf-yrbcrl/capz-conf-yrbcrl to be deleted [1mSTEP:[0m Waiting for cluster capz-conf-yrbcrl to be deleted [38;5;243m@ 01/28/23 00:18:15.567[0m Jan 28 00:26:05.927: INFO: Deleting namespace used for hosting the "conformance-tests" test spec INFO: Deleting namespace capz-conf-yrbcrl Jan 28 00:26:05.961: INFO: Checking if any resources are left over in Azure for spec "conformance-tests" [1mSTEP:[0m Redacting sensitive information from logs [38;5;243m@ 01/28/23 00:26:06.497[0m [38;5;9m• [FAILED] [1353.931 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 180.001s. Expected success, but got an error: <*errors.withStack | 0xc00109f950>: { error: <*errors.withMessage | 0xc00068e3c0>{ cause: <*url.Error | 0xc002a97ce0>{ Op: "Get", URL: "https://capz-conf-yrbcrl-6e411607.uksouth.cloudapp.azure.com:6443/version", Err: <*net.OpError | 0xc0012a0af0>{ Op: "dial", Net: "tcp", Source: nil, ... skipping 33 lines ... [0m[1m[ReportAfterSuite] Autogenerated ReportAfterSuite for --junit-report[0m [38;5;243mautogenerated by Ginkgo[0m [38;5;10m[ReportAfterSuite] PASSED [0.006 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 1542.396 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 --- FAIL: TestE2E (1542.40s) FAIL [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.0[0m Ginkgo ran 1 suite in 28m8.444765484s 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 ...