This job view page is being replaced by Spyglass soon.
Check out the new job view.
Error lines from build-log.txt
... skipping 183 lines ...
#18 exporting layers 0.4s done
#18 writing image sha256:b04911d677590d7b49a681c9ea1499b75ac1ee8773a9b5cb6b53ae88939b3179 done
#18 naming to gcr.io/k8s-staging-cluster-api/capv-manager:e2e done
#18 DONE 0.4s
#9 [builder 1/6] FROM docker.io/library/golang:1.19.3@sha256:10e3c0f39f8e237baa5b66c5295c578cac42a99536cc9333d8505324a82407d9
WARNING: failed to get git remote url: fatal: No remote configured to list refs from.
Activated service account credentials for: [capv-prow@cluster-api-provider-vsphere.iam.gserviceaccount.com]
Copying file:///logs/artifacts/tempContainers/image.tar [Content-Type=application/x-tar]...
/ [0 files][ 0.0 B/ 74.6 MiB]
-
- [1 files][ 74.6 MiB/ 74.6 MiB]
Operation completed over 1 objects/74.6 MiB.
make -C /home/prow/go/src/sigs.k8s.io/cluster-api-provider-vsphere/hack/tools ginkgo
make[1]: Entering directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-vsphere/hack/tools'
... skipping 129 lines ...
#18 exporting to image
#18 exporting layers done
#18 writing image sha256:b04911d677590d7b49a681c9ea1499b75ac1ee8773a9b5cb6b53ae88939b3179 done
#18 naming to gcr.io/k8s-staging-cluster-api/capv-manager:e2e done
#18 DONE 0.0s
WARNING: failed to get git remote url: fatal: No remote configured to list refs from.
make release-manifests
make[1]: Entering directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-vsphere'
make manifests STAGE=release MANIFEST_DIR=out PULL_POLICY=IfNotPresent IMAGE=gcr.io/cluster-api-provider-vsphere/release/manager:v1.6.0
make[2]: Entering directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-vsphere'
make generate-flavors FLAVOR_DIR=out
make[3]: Entering directory '/home/prow/go/src/sigs.k8s.io/cluster-api-provider-vsphere'
... skipping 326 lines ...
[1mSTEP:[0m Waiting for deployment node-drain-yjyesi-unevictable-workload/unevictable-pod-h2b to be available [38;5;243m@ 02/01/23 05:42:16.212[0m
[1mSTEP:[0m Scale down the controlplane of the workload cluster and make sure that nodes running workload can be deleted even the draining process is blocked. [38;5;243m@ 02/01/23 05:42:26.515[0m
INFO: Scaling controlplane node-drain-yjyesi/node-drain-bggavl from 3 to 1 replicas
INFO: Waiting for correct number of replicas to exist
[1mSTEP:[0m PASSED! [38;5;243m@ 02/01/23 05:46:17.114[0m
[1mSTEP:[0m Dumping logs from the "node-drain-bggavl" workload cluster [38;5;243m@ 02/01/23 05:46:17.114[0m
Failed to get logs for Machine node-drain-bggavl-n7np8, Cluster node-drain-yjyesi/node-drain-bggavl: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
[1mSTEP:[0m Dumping all the Cluster API resources in the "node-drain-yjyesi" namespace [38;5;243m@ 02/01/23 05:46:19.11[0m
[1mSTEP:[0m Deleting cluster node-drain-yjyesi/node-drain-bggavl [38;5;243m@ 02/01/23 05:46:19.361[0m
[1mSTEP:[0m Deleting cluster node-drain-bggavl [38;5;243m@ 02/01/23 05:46:19.385[0m
INFO: Waiting for the Cluster node-drain-yjyesi/node-drain-bggavl to be deleted
[1mSTEP:[0m Waiting for cluster node-drain-bggavl to be deleted [38;5;243m@ 02/01/23 05:46:19.399[0m
[1mSTEP:[0m Deleting namespace used for hosting the "node-drain" test spec [38;5;243m@ 02/01/23 05:46:39.412[0m
... skipping 57 lines ...
INFO: Waiting for MachineDeployment rollout for MachineDeploymentTopology "md-0" (class "quick-start-worker") to complete.
[1mSTEP:[0m Deleting a MachineDeploymentTopology in the Cluster Topology and wait for associated MachineDeployment to be deleted [38;5;243m@ 02/01/23 05:50:51.16[0m
INFO: Removing MachineDeploymentTopology from the Cluster Topology.
INFO: Waiting for MachineDeployment to be deleted.
[1mSTEP:[0m PASSED! [38;5;243m@ 02/01/23 05:51:01.23[0m
[1mSTEP:[0m Dumping logs from the "clusterclass-changes-dqvgd0" workload cluster [38;5;243m@ 02/01/23 05:51:01.23[0m
Failed to get logs for Machine clusterclass-changes-dqvgd0-hqh94-xpx6f, Cluster clusterclass-changes-g96dhd/clusterclass-changes-dqvgd0: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
[1mSTEP:[0m Dumping all the Cluster API resources in the "clusterclass-changes-g96dhd" namespace [38;5;243m@ 02/01/23 05:51:03.404[0m
[1mSTEP:[0m Deleting cluster clusterclass-changes-g96dhd/clusterclass-changes-dqvgd0 [38;5;243m@ 02/01/23 05:51:03.679[0m
[1mSTEP:[0m Deleting cluster clusterclass-changes-dqvgd0 [38;5;243m@ 02/01/23 05:51:03.697[0m
INFO: Waiting for the Cluster clusterclass-changes-g96dhd/clusterclass-changes-dqvgd0 to be deleted
[1mSTEP:[0m Waiting for cluster clusterclass-changes-dqvgd0 to be deleted [38;5;243m@ 02/01/23 05:51:03.707[0m
[1mSTEP:[0m Deleting namespace used for hosting the "clusterclass-changes" test spec [38;5;243m@ 02/01/23 05:51:23.721[0m
... skipping 44 lines ...
INFO: Waiting for the machine deployments to be provisioned
[1mSTEP:[0m Waiting for the workload nodes to exist [38;5;243m@ 02/01/23 05:54:44.948[0m
[1mSTEP:[0m Checking all the machines controlled by quick-start-04z439-md-0 are in the "<None>" failure domain [38;5;243m@ 02/01/23 05:55:14.988[0m
INFO: Waiting for the machine pools to be provisioned
[1mSTEP:[0m PASSED! [38;5;243m@ 02/01/23 05:55:15.024[0m
[1mSTEP:[0m Dumping logs from the "quick-start-04z439" workload cluster [38;5;243m@ 02/01/23 05:55:15.024[0m
Failed to get logs for Machine quick-start-04z439-9pdcw, Cluster quick-start-uamx1q/quick-start-04z439: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine quick-start-04z439-md-0-74d56c4579-tt2wh, Cluster quick-start-uamx1q/quick-start-04z439: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
[1mSTEP:[0m Dumping all the Cluster API resources in the "quick-start-uamx1q" namespace [38;5;243m@ 02/01/23 05:55:19.411[0m
[1mSTEP:[0m Deleting cluster quick-start-uamx1q/quick-start-04z439 [38;5;243m@ 02/01/23 05:55:19.68[0m
[1mSTEP:[0m Deleting cluster quick-start-04z439 [38;5;243m@ 02/01/23 05:55:19.698[0m
INFO: Waiting for the Cluster quick-start-uamx1q/quick-start-04z439 to be deleted
[1mSTEP:[0m Waiting for cluster quick-start-04z439 to be deleted [38;5;243m@ 02/01/23 05:55:19.71[0m
[1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 02/01/23 05:55:49.727[0m
... skipping 50 lines ...
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
[1mSTEP:[0m PASSED! [38;5;243m@ 02/01/23 06:01:21.137[0m
[1mSTEP:[0m Dumping logs from the "md-rollout-tq5fir" workload cluster [38;5;243m@ 02/01/23 06:01:21.137[0m
Failed to get logs for Machine md-rollout-tq5fir-68n4k, Cluster md-rollout-fpy1kf/md-rollout-tq5fir: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine md-rollout-tq5fir-md-0-54659b6bd5-ngvcf, Cluster md-rollout-fpy1kf/md-rollout-tq5fir: 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-fpy1kf" namespace [38;5;243m@ 02/01/23 06:01:25.717[0m
[1mSTEP:[0m Deleting cluster md-rollout-fpy1kf/md-rollout-tq5fir [38;5;243m@ 02/01/23 06:01:25.984[0m
[1mSTEP:[0m Deleting cluster md-rollout-tq5fir [38;5;243m@ 02/01/23 06:01:26.003[0m
INFO: Waiting for the Cluster md-rollout-fpy1kf/md-rollout-tq5fir to be deleted
[1mSTEP:[0m Waiting for cluster md-rollout-tq5fir to be deleted [38;5;243m@ 02/01/23 06:01:26.017[0m
[1mSTEP:[0m Deleting namespace used for hosting the "md-rollout" test spec [38;5;243m@ 02/01/23 06:01:56.033[0m
... skipping 50 lines ...
INFO: Waiting for correct number of replicas to exist
[1mSTEP:[0m Scaling the MachineDeployment down to 1 [38;5;243m@ 02/01/23 06:07:27.842[0m
INFO: Scaling machine deployment md-scale-2lyt0w/md-scale-159d0u-md-0 from 3 to 1 replicas
INFO: Waiting for correct number of replicas to exist
[1mSTEP:[0m PASSED! [38;5;243m@ 02/01/23 06:07:37.956[0m
[1mSTEP:[0m Dumping logs from the "md-scale-159d0u" workload cluster [38;5;243m@ 02/01/23 06:07:37.956[0m
Failed to get logs for Machine md-scale-159d0u-8bcpd, Cluster md-scale-2lyt0w/md-scale-159d0u: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine md-scale-159d0u-md-0-8b577bddf-xshh5, Cluster md-scale-2lyt0w/md-scale-159d0u: 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-scale-2lyt0w" namespace [38;5;243m@ 02/01/23 06:07:42.585[0m
[1mSTEP:[0m Deleting cluster md-scale-2lyt0w/md-scale-159d0u [38;5;243m@ 02/01/23 06:07:42.848[0m
[1mSTEP:[0m Deleting cluster md-scale-159d0u [38;5;243m@ 02/01/23 06:07:42.864[0m
INFO: Waiting for the Cluster md-scale-2lyt0w/md-scale-159d0u to be deleted
[1mSTEP:[0m Waiting for cluster md-scale-159d0u to be deleted [38;5;243m@ 02/01/23 06:07:42.875[0m
[1mSTEP:[0m Deleting namespace used for hosting the "md-scale" test spec [38;5;243m@ 02/01/23 06:08:12.892[0m
... skipping 110 lines ...
INFO: Waiting for the machine deployments to be provisioned
[1mSTEP:[0m Waiting for the workload nodes to exist [38;5;243m@ 02/01/23 06:18:20.953[0m
[1mSTEP:[0m Checking all the machines controlled by quick-start-rabjxg-md-0-g6wkz are in the "<None>" failure domain [38;5;243m@ 02/01/23 06:19:11.015[0m
INFO: Waiting for the machine pools to be provisioned
[1mSTEP:[0m PASSED! [38;5;243m@ 02/01/23 06:19:11.055[0m
[1mSTEP:[0m Dumping logs from the "quick-start-rabjxg" workload cluster [38;5;243m@ 02/01/23 06:19:11.055[0m
Failed to get logs for Machine quick-start-rabjxg-lkfmz-c2tqd, Cluster quick-start-aso6a1/quick-start-rabjxg: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine quick-start-rabjxg-md-0-g6wkz-7cdff7465-vhj2s, Cluster quick-start-aso6a1/quick-start-rabjxg: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
[1mSTEP:[0m Dumping all the Cluster API resources in the "quick-start-aso6a1" namespace [38;5;243m@ 02/01/23 06:19:15.76[0m
[1mSTEP:[0m Deleting cluster quick-start-aso6a1/quick-start-rabjxg [38;5;243m@ 02/01/23 06:19:16.051[0m
[1mSTEP:[0m Deleting cluster quick-start-rabjxg [38;5;243m@ 02/01/23 06:19:16.069[0m
INFO: Waiting for the Cluster quick-start-aso6a1/quick-start-rabjxg to be deleted
[1mSTEP:[0m Waiting for cluster quick-start-rabjxg to be deleted [38;5;243m@ 02/01/23 06:19:16.08[0m
[1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 02/01/23 06:19:46.1[0m
... skipping 99 lines ...
[1mSTEP:[0m Waiting for the control plane to be ready [38;5;243m@ 02/01/23 06:25:50.67[0m
[1mSTEP:[0m Checking all the control plane machines are in the expected failure domains [38;5;243m@ 02/01/23 06:26:00.685[0m
INFO: Waiting for the machine deployments to be provisioned
[1mSTEP:[0m Waiting for the workload nodes to exist [38;5;243m@ 02/01/23 06:26:00.707[0m
[38;5;214m[TIMEDOUT][0m in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/quick_start.go:78 [38;5;243m@ 02/01/23 06:26:46.631[0m
[1mSTEP:[0m Dumping logs from the "quick-start-ul4jr0" workload cluster [38;5;243m@ 02/01/23 06:26:46.633[0m
Failed to get logs for Machine quick-start-ul4jr0-md-0-bfdd7bf9b-ftjf8, Cluster quick-start-x1nthn/quick-start-ul4jr0: dialing host IP address at : dial tcp :22: connect: connection refused
Failed to get logs for Machine quick-start-ul4jr0-wccxs, Cluster quick-start-x1nthn/quick-start-ul4jr0: dialing host IP address at 192.168.6.57: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
[1mSTEP:[0m Dumping all the Cluster API resources in the "quick-start-x1nthn" namespace [38;5;243m@ 02/01/23 06:26:47.835[0m
[1mSTEP:[0m Deleting cluster quick-start-x1nthn/quick-start-ul4jr0 [38;5;243m@ 02/01/23 06:26:48.16[0m
[1mSTEP:[0m Deleting cluster quick-start-ul4jr0 [38;5;243m@ 02/01/23 06:26:48.176[0m
INFO: Waiting for the Cluster quick-start-x1nthn/quick-start-ul4jr0 to be deleted
[1mSTEP:[0m Waiting for cluster quick-start-ul4jr0 to be deleted [38;5;243m@ 02/01/23 06:26:48.187[0m
[38;5;214m[TIMEDOUT][0m in [AfterEach] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/quick_start.go:109 [38;5;243m@ 02/01/23 06:27:16.634[0m
... skipping 76 lines ...
[38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc0026c06f0, 0x27}, {0xc0026c0720, 0x22}, {0xc0025e0044, 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 33227 [sync.Cond.Wait][0m
... skipping 18 lines ...
[38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc0018f44c0, 0x3a}, {0xc0018f4500, 0x35}, {0xc00119fba0, 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}}, {{0xc0020d5c50, 0x28}, {0xc0020d5c80, 0x23}, {0xc0008e2a54, 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 33230 [sync.Cond.Wait][0m
... skipping 18 lines ...
[38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc0018f57c0, 0x3e}, {0xc0018f5800, 0x39}, {0xc0018230b0, 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 29 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 33269 [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 {
There were [1m[38;5;9madditional failures[0m detected. To view them in detail run [1mginkgo -vv[0m
... skipping 9 lines ...
[38;5;9m[1mSummarizing 1 Failure:[0m
[38;5;214m[TIMEDOUT][0m [0mCluster creation with [Ignition] bootstrap [PR-Blocking] [38;5;214m[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[1mRan 10 of 17 Specs in 3580.098 seconds[0m
[38;5;9m[1mFAIL! - Suite Timeout Elapsed[0m -- [38;5;10m[1m9 Passed[0m | [38;5;9m[1m1 Failed[0m | [38;5;11m[1m1 Pending[0m | [38;5;14m[1m6 Skipped[0m
--- FAIL: TestE2E (3580.10s)
FAIL
Ginkgo ran 1 suite in 1h0m31.516315571s
Test Suite Failed
real 60m31.534s
user 5m30.914s
sys 1m1.684s
make: *** [Makefile:183: e2e] Error 1
Releasing IP claims
ipclaim.ipam.metal3.io "ip-claim-a5dc82d59ad495484dcdd62fc37178f983f4a889" deleted
ipclaim.ipam.metal3.io "workload-ip-claim-dfd272f6d8b467f466115dc45225c705b826b529" 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 ...