periodic-cluster-api-provider-vsphere-e2e-main #1617028710957846528
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 1h4m |
| Revision | main |
... skipping 568 lines ... INFO: Waiting for the cluster infrastructure to be provisioned [1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/22/23 05:25:11.677[0m INFO: Waiting for control plane to be initialized INFO: Waiting for the first control plane machine managed by quick-start-bw75xv/quick-start-pjqv8d to be provisioned [1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/22/23 05:25:41.75[0m [38;5;9m[FAILED][0m in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154 [38;5;243m@ 01/22/23 05:35:41.751[0m [1mSTEP:[0m Dumping logs from the "quick-start-pjqv8d" workload cluster [38;5;243m@ 01/22/23 05:35:41.751[0m Failed to get logs for Machine quick-start-pjqv8d-f5gcf, Cluster quick-start-bw75xv/quick-start-pjqv8d: dialing host IP address at 192.168.6.117: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain Failed to get logs for Machine quick-start-pjqv8d-md-0-66996d6c48-wfkcx, Cluster quick-start-bw75xv/quick-start-pjqv8d: dialing host IP address at : dial tcp :22: connect: connection refused [1mSTEP:[0m Dumping all the Cluster API resources in the "quick-start-bw75xv" namespace [38;5;243m@ 01/22/23 05:35:43.029[0m [1mSTEP:[0m Deleting cluster quick-start-bw75xv/quick-start-pjqv8d [38;5;243m@ 01/22/23 05:35:43.323[0m [1mSTEP:[0m Deleting cluster quick-start-pjqv8d [38;5;243m@ 01/22/23 05:35:43.35[0m INFO: Waiting for the Cluster quick-start-bw75xv/quick-start-pjqv8d to be deleted [1mSTEP:[0m Waiting for cluster quick-start-pjqv8d to be deleted [38;5;243m@ 01/22/23 05:35:43.397[0m [1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 01/22/23 05:36:03.413[0m INFO: Deleting namespace quick-start-bw75xv [38;5;9m• [FAILED] [656.458 seconds][0m [0mCluster creation with [Ignition] bootstrap [PR-Blocking] [38;5;9m[1m[It] Should create a workload cluster[0m [38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/quick_start.go:78[0m [38;5;9m[FAILED] Timed out after 600.000s. No Control Plane machines came into existence. Expected <bool>: false to be true[0m [38;5;9mIn [1m[It][0m[38;5;9m at: [1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154[0m [38;5;243m@ 01/22/23 05:35:41.751[0m [38;5;243m------------------------------[0m ... skipping 31 lines ... INFO: Waiting for the cluster infrastructure to be provisioned [1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/22/23 05:36:04.762[0m INFO: Waiting for control plane to be initialized INFO: Waiting for the first control plane machine managed by capv-e2e-096q5e/storage-policy-sozugs to be provisioned [1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/22/23 05:36:24.794[0m [38;5;9m[FAILED][0m in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154 [38;5;243m@ 01/22/23 05:46:24.798[0m [1mSTEP:[0m Dumping all the Cluster API resources in the "capv-e2e-096q5e" namespace [38;5;243m@ 01/22/23 05:46:24.798[0m [1mSTEP:[0m cleaning up namespace: capv-e2e-096q5e [38;5;243m@ 01/22/23 05:46:25.089[0m [1mSTEP:[0m Deleting cluster storage-policy-sozugs [38;5;243m@ 01/22/23 05:46:25.107[0m INFO: Waiting for the Cluster capv-e2e-096q5e/storage-policy-sozugs to be deleted [1mSTEP:[0m Waiting for cluster storage-policy-sozugs to be deleted [38;5;243m@ 01/22/23 05:46:25.12[0m [1mSTEP:[0m Deleting namespace used for hosting test spec [38;5;243m@ 01/22/23 05:46:45.135[0m INFO: Deleting namespace capv-e2e-096q5e [38;5;9m• [FAILED] [641.719 seconds][0m [0mCluster creation with storage policy [38;5;9m[1m[It] should create a cluster successfully[0m [38;5;243m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-vsphere/test/e2e/storage_policy_test.go:57[0m [38;5;9m[FAILED] Timed out after 600.003s. No Control Plane machines came into existence. Expected <bool>: false to be true[0m [38;5;9mIn [1m[It][0m[38;5;9m at: [1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154[0m [38;5;243m@ 01/22/23 05:46:24.798[0m [38;5;243m------------------------------[0m ... skipping 45 lines ... [1mSTEP:[0m Upgrading MachineDeployment Infrastructure ref and wait for rolling upgrade [38;5;243m@ 01/22/23 05:51:46.715[0m INFO: Patching the new infrastructure ref to Machine Deployment md-rollout-ultgm2/md-rollout-oiblun-md-0 INFO: Waiting for rolling upgrade to start. INFO: Waiting for MachineDeployment rolling upgrade to start INFO: Waiting for rolling upgrade to complete. INFO: Waiting for MachineDeployment rolling upgrade to complete [38;5;9m[FAILED][0m in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/machinedeployment_helpers.go:294 [38;5;243m@ 01/22/23 06:07:46.786[0m [1mSTEP:[0m Dumping logs from the "md-rollout-oiblun" workload cluster [38;5;243m@ 01/22/23 06:07:46.786[0m Failed to get logs for Machine md-rollout-oiblun-md-0-6564b9fc-97x9d, Cluster md-rollout-ultgm2/md-rollout-oiblun: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine md-rollout-oiblun-md-0-7b7c5bc455-mxqxl, Cluster md-rollout-ultgm2/md-rollout-oiblun: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine md-rollout-oiblun-w7cqs, Cluster md-rollout-ultgm2/md-rollout-oiblun: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 [1mSTEP:[0m Dumping all the Cluster API resources in the "md-rollout-ultgm2" namespace [38;5;243m@ 01/22/23 06:07:54.046[0m [1mSTEP:[0m Deleting cluster md-rollout-ultgm2/md-rollout-oiblun [38;5;243m@ 01/22/23 06:07:54.345[0m [1mSTEP:[0m Deleting cluster md-rollout-oiblun [38;5;243m@ 01/22/23 06:07:54.364[0m INFO: Waiting for the Cluster md-rollout-ultgm2/md-rollout-oiblun to be deleted [1mSTEP:[0m Waiting for cluster md-rollout-oiblun to be deleted [38;5;243m@ 01/22/23 06:07:54.377[0m [1mSTEP:[0m Deleting namespace used for hosting the "md-rollout" test spec [38;5;243m@ 01/22/23 06:08:14.395[0m INFO: Deleting namespace md-rollout-ultgm2 [38;5;9m• [FAILED] [1289.259 seconds][0m [0mClusterAPI Machine Deployment Tests [38;5;243mRunning the MachineDeployment rollout spec [38;5;9m[1m[It] Should successfully upgrade Machines upon changes in relevant MachineDeployment fields[0m [38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/md_rollout.go:71[0m [38;5;9m[FAILED] Timed out after 900.000s. Expected <bool>: false to be true[0m [38;5;9mIn [1m[It][0m[38;5;9m at: [1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/machinedeployment_helpers.go:294[0m [38;5;243m@ 01/22/23 06:07:46.786[0m [38;5;243m------------------------------[0m [0mWhen testing unhealthy machines remediation [0m[1mShould successfully trigger machine deployment remediation[0m ... skipping 31 lines ... INFO: Waiting for the cluster infrastructure to be provisioned [1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/22/23 06:08:15.671[0m INFO: Waiting for control plane to be initialized INFO: Waiting for the first control plane machine managed by mhc-remediation-pp7otj/mhc-remediation-hsyjmq to be provisioned [1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/22/23 06:09:05.723[0m [38;5;9m[FAILED][0m in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154 [38;5;243m@ 01/22/23 06:19:05.723[0m [1mSTEP:[0m Dumping logs from the "mhc-remediation-hsyjmq" workload cluster [38;5;243m@ 01/22/23 06:19:05.723[0m Failed to get logs for Machine mhc-remediation-hsyjmq-kkvf9, Cluster mhc-remediation-pp7otj/mhc-remediation-hsyjmq: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-hsyjmq-md-0-75c85b467b-47b8b, Cluster mhc-remediation-pp7otj/mhc-remediation-hsyjmq: dialing host IP address at : dial tcp :22: connect: connection refused [1mSTEP:[0m Dumping all the Cluster API resources in the "mhc-remediation-pp7otj" namespace [38;5;243m@ 01/22/23 06:19:07.917[0m [1mSTEP:[0m Deleting cluster mhc-remediation-pp7otj/mhc-remediation-hsyjmq [38;5;243m@ 01/22/23 06:19:08.19[0m [1mSTEP:[0m Deleting cluster mhc-remediation-hsyjmq [38;5;243m@ 01/22/23 06:19:08.21[0m INFO: Waiting for the Cluster mhc-remediation-pp7otj/mhc-remediation-hsyjmq to be deleted [1mSTEP:[0m Waiting for cluster mhc-remediation-hsyjmq to be deleted [38;5;243m@ 01/22/23 06:19:08.227[0m [1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 01/22/23 06:19:28.243[0m INFO: Deleting namespace mhc-remediation-pp7otj [38;5;9m• [FAILED] [673.843 seconds][0m [0mWhen testing unhealthy machines remediation [38;5;9m[1m[It] Should successfully trigger machine deployment remediation[0m [38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/mhc_remediations.go:83[0m [38;5;9m[FAILED] Timed out after 600.000s. No Control Plane machines came into existence. Expected <bool>: false to be true[0m [38;5;9mIn [1m[It][0m[38;5;9m at: [1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154[0m [38;5;243m@ 01/22/23 06:19:05.723[0m [38;5;243m------------------------------[0m ... skipping 34 lines ... [1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/22/23 06:19:29.582[0m INFO: Waiting for control plane to be initialized INFO: Waiting for the first control plane machine managed by mhc-remediation-k6saxq/mhc-remediation-12mghd to be provisioned [1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/22/23 06:20:19.633[0m [38;5;214m[TIMEDOUT][0m in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/mhc_remediations.go:116 [38;5;243m@ 01/22/23 06:21:57.878[0m [1mSTEP:[0m Dumping logs from the "mhc-remediation-12mghd" workload cluster [38;5;243m@ 01/22/23 06:21:57.88[0m Failed to get logs for Machine mhc-remediation-12mghd-md-0-58bf596478-lqsqf, Cluster mhc-remediation-k6saxq/mhc-remediation-12mghd: dialing host IP address at : dial tcp :22: connect: connection refused Failed to get logs for Machine mhc-remediation-12mghd-sftvn, Cluster mhc-remediation-k6saxq/mhc-remediation-12mghd: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 [1mSTEP:[0m Dumping all the Cluster API resources in the "mhc-remediation-k6saxq" namespace [38;5;243m@ 01/22/23 06:21:59.791[0m [1mSTEP:[0m Deleting cluster mhc-remediation-k6saxq/mhc-remediation-12mghd [38;5;243m@ 01/22/23 06:22:00.083[0m [1mSTEP:[0m Deleting cluster mhc-remediation-12mghd [38;5;243m@ 01/22/23 06:22:00.099[0m INFO: Waiting for the Cluster mhc-remediation-k6saxq/mhc-remediation-12mghd to be deleted [1mSTEP:[0m Waiting for cluster mhc-remediation-12mghd to be deleted [38;5;243m@ 01/22/23 06:22:00.111[0m [1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 01/22/23 06:22:20.126[0m ... skipping 69 lines ... | for { [1m[38;5;214m> select {[0m | case <-ctx.Done(): | return [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225[0m | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment)) | [1m[38;5;214m> go func() {[0m | defer GinkgoRecover() | for { [38;5;214mgoroutine 45898 [chan receive, 2 minutes][0m ... skipping 41 lines ... [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc00265c810, 0x27}, {0xc00265c840, 0x22}, {0xc0011bc1a4, 0xb}, ...}, ...}, ...)[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186[0m | out := bufio.NewWriter(f) | defer out.Flush() [1m[38;5;214m> _, err = out.ReadFrom(podLogs)[0m | if err != nil && err != io.ErrUnexpectedEOF { | // Failing to stream logs should not cause the test to fail [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161[0m | | // Watch each container's logs in a goroutine so we can stream them all concurrently. [1m[38;5;214m> go func(pod corev1.Pod, container corev1.Container) {[0m | defer GinkgoRecover() ... skipping 21 lines ... [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc00222dce0, 0x28}, {0xc00222dd10, 0x23}, {0xc0020e5184, 0xb}, ...}, ...}, ...)[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186[0m | out := bufio.NewWriter(f) | defer out.Flush() [1m[38;5;214m> _, err = out.ReadFrom(podLogs)[0m | if err != nil && err != io.ErrUnexpectedEOF { | // Failing to stream logs should not cause the test to fail [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161[0m | | // Watch each container's logs in a goroutine so we can stream them all concurrently. [1m[38;5;214m> go func(pod corev1.Pod, container corev1.Container) {[0m | defer GinkgoRecover() ... skipping 6 lines ... | for { [1m[38;5;214m> select {[0m | case <-ctx.Done(): | return [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225[0m | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment)) | [1m[38;5;214m> go func() {[0m | defer GinkgoRecover() | for { [38;5;214mgoroutine 32835 [select][0m ... skipping 3 lines ... | for { [1m[38;5;214m> select {[0m | case <-ctx.Done(): | return [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225[0m | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment)) | [1m[38;5;214m> go func() {[0m | defer GinkgoRecover() | for { [38;5;214mgoroutine 32747 [sync.Cond.Wait, 2 minutes][0m ... skipping 18 lines ... [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc001516600, 0x3a}, {0xc001516640, 0x35}, {0xc000fa68a0, 0x1d}, ...}, ...}, ...)[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186[0m | out := bufio.NewWriter(f) | defer out.Flush() [1m[38;5;214m> _, err = out.ReadFrom(podLogs)[0m | if err != nil && err != io.ErrUnexpectedEOF { | // Failing to stream logs should not cause the test to fail [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161[0m | | // Watch each container's logs in a goroutine so we can stream them all concurrently. [1m[38;5;214m> go func(pod corev1.Pod, container corev1.Container) {[0m | defer GinkgoRecover() ... skipping 21 lines ... [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc000a51440, 0x3e}, {0xc000a51480, 0x39}, {0xc000fd9260, 0x21}, ...}, ...}, ...)[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186[0m | out := bufio.NewWriter(f) | defer out.Flush() [1m[38;5;214m> _, err = out.ReadFrom(podLogs)[0m | if err != nil && err != io.ErrUnexpectedEOF { | // Failing to stream logs should not cause the test to fail [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161[0m | | // Watch each container's logs in a goroutine so we can stream them all concurrently. [1m[38;5;214m> go func(pod corev1.Pod, container corev1.Container) {[0m | defer GinkgoRecover() ... skipping 6 lines ... | for { [1m[38;5;214m> select {[0m | case <-ctx.Done(): | return [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225[0m | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment)) | [1m[38;5;214m> go func() {[0m | defer GinkgoRecover() | for { [38;5;243m------------------------------[0m [38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m[38;5;14mS[0m ... skipping 8 lines ... [1mSTEP:[0m Cleaning up the vSphere session [38;5;243m@ 01/22/23 06:22:20.148[0m [1mSTEP:[0m Tearing down the management cluster [38;5;243m@ 01/22/23 06:22:20.32[0m [38;5;10m[SynchronizedAfterSuite] PASSED [1.686 seconds][0m [38;5;243m------------------------------[0m [38;5;9m[1mSummarizing 5 Failures:[0m [38;5;9m[FAIL][0m [0mCluster creation with [Ignition] bootstrap [PR-Blocking] [38;5;9m[1m[It] Should create a workload cluster[0m [38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154[0m [38;5;9m[FAIL][0m [0mCluster creation with storage policy [38;5;9m[1m[It] should create a cluster successfully[0m [38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154[0m [38;5;9m[FAIL][0m [0mClusterAPI Machine Deployment Tests [38;5;243mRunning the MachineDeployment rollout spec [38;5;9m[1m[It] Should successfully upgrade Machines upon changes in relevant MachineDeployment fields[0m [38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/machinedeployment_helpers.go:294[0m [38;5;9m[FAIL][0m [0mWhen testing unhealthy machines remediation [38;5;9m[1m[It] Should successfully trigger machine deployment remediation[0m [38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154[0m [38;5;214m[TIMEDOUT][0m [0mWhen testing unhealthy machines remediation [38;5;214m[1m[It] Should successfully trigger KCP remediation[0m [38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/mhc_remediations.go:116[0m [38;5;9m[1mRan 5 of 17 Specs in 3569.608 seconds[0m [38;5;9m[1mFAIL! - Suite Timeout Elapsed[0m -- [38;5;10m[1m0 Passed[0m | [38;5;9m[1m5 Failed[0m | [38;5;11m[1m1 Pending[0m | [38;5;14m[1m11 Skipped[0m --- FAIL: TestE2E (3569.61s) FAIL Ginkgo ran 1 suite in 1h0m24.044765646s Test Suite Failed real 60m24.069s user 5m42.005s sys 1m8.018s make: *** [Makefile:183: e2e] Error 1 Releasing IP claims ipclaim.ipam.metal3.io "ip-claim-6367c23dd609c7cbe074f68b932f4c67994e7fe4" deleted ipclaim.ipam.metal3.io "workload-ip-claim-e162098fc94ffddee43e933f81051a8d450a365d" deleted vpn WARNING: [capv-prow@cluster-api-provider-vsphere.iam.gserviceaccount.com] appears to be a service account. Service account tokens cannot be revoked, but they will expire automatically. To prevent use of the service account token earlier than the expiration, delete or disable the parent service account. To explicitly delete the key associated with the service account use `gcloud iam service-accounts keys delete` instead`. Revoked credentials: ... skipping 13 lines ...