This job view page is being replaced by Spyglass soon.
Check out the new job view.
Error lines from build-log.txt
... skipping 178 lines ...
#18 exporting to image
#18 exporting layers
#18 exporting layers 0.4s done
#18 writing image sha256:0e8bc5221d49ade046509c059be2ce4a327814d3c9c7ba1d24d59fab4986b2ce done
#18 naming to gcr.io/k8s-staging-cluster-api/capv-manager:e2e done
#18 DONE 0.4s
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:0e8bc5221d49ade046509c059be2ce4a327814d3c9c7ba1d24d59fab4986b2ce 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 243 lines ...
INFO: Waiting for the cluster infrastructure to be provisioned
[1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/31/23 05:29:12.998[0m
INFO: Waiting for control plane to be initialized
INFO: Waiting for the first control plane machine managed by node-drain-1pesz2/node-drain-gpf4zu to be provisioned
[1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/31/23 05:29:43.033[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/31/23 05:39:43.034[0m
[1mSTEP:[0m Dumping logs from the "node-drain-gpf4zu" workload cluster [38;5;243m@ 01/31/23 05:39:43.034[0m
Failed to get logs for Machine node-drain-gpf4zu-hrl2f, Cluster node-drain-1pesz2/node-drain-gpf4zu: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine node-drain-gpf4zu-md-0-84985bb747-xxwgq, Cluster node-drain-1pesz2/node-drain-gpf4zu: dialing host IP address at : dial tcp :22: connect: connection refused
[1mSTEP:[0m Dumping all the Cluster API resources in the "node-drain-1pesz2" namespace [38;5;243m@ 01/31/23 05:39:45.361[0m
[1mSTEP:[0m Deleting cluster node-drain-1pesz2/node-drain-gpf4zu [38;5;243m@ 01/31/23 05:39:45.617[0m
[1mSTEP:[0m Deleting cluster node-drain-gpf4zu [38;5;243m@ 01/31/23 05:39:45.635[0m
INFO: Waiting for the Cluster node-drain-1pesz2/node-drain-gpf4zu to be deleted
[1mSTEP:[0m Waiting for cluster node-drain-gpf4zu to be deleted [38;5;243m@ 01/31/23 05:39:45.647[0m
[1mSTEP:[0m Deleting namespace used for hosting the "node-drain" test spec [38;5;243m@ 01/31/23 05:40:05.662[0m
INFO: Deleting namespace node-drain-1pesz2
[38;5;9m• [FAILED] [655.064 seconds][0m
[0mWhen testing node drain timeout [38;5;9m[1m[It] A node should be forcefully removed if it cannot be drained in time[0m
[38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/node_drain_timeout.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/31/23 05:39:43.034[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/31/23 05:40:06.752[0m
INFO: Waiting for control plane to be initialized
INFO: Waiting for the first control plane machine managed by anti-affinity-e2e-7xq316/anti-affinity-b10t9g to be provisioned
[1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/31/23 05:40:56.809[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/31/23 05:50:56.809[0m
[1mSTEP:[0m Dumping all the Cluster API resources in the "anti-affinity-e2e-7xq316" namespace [38;5;243m@ 01/31/23 05:50:56.81[0m
[1mSTEP:[0m cleaning up namespace: anti-affinity-e2e-7xq316 [38;5;243m@ 01/31/23 05:50:57.114[0m
[1mSTEP:[0m Deleting cluster anti-affinity-b10t9g [38;5;243m@ 01/31/23 05:50:57.137[0m
INFO: Waiting for the Cluster anti-affinity-e2e-7xq316/anti-affinity-b10t9g to be deleted
[1mSTEP:[0m Waiting for cluster anti-affinity-b10t9g to be deleted [38;5;243m@ 01/31/23 05:50:57.149[0m
[1mSTEP:[0m Deleting namespace used for hosting test spec [38;5;243m@ 01/31/23 05:51:17.165[0m
INFO: Deleting namespace anti-affinity-e2e-7xq316
[38;5;9m• [FAILED] [671.500 seconds][0m
[0mCluster creation with anti affined nodes [38;5;9m[1m[It] should create a cluster with anti-affined nodes[0m
[38;5;243m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-vsphere/test/e2e/anti_affinity_test.go:61[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/31/23 05:50:56.809[0m
[38;5;243m------------------------------[0m
... skipping 37 lines ...
INFO: Waiting for control plane to be ready
INFO: Waiting for control plane md-rollout-6d5dkh/md-rollout-4wmdz3 to be ready (implies underlying nodes to be ready as well)
[1mSTEP:[0m Waiting for the control plane to be ready [38;5;243m@ 01/31/23 05:59:48.642[0m
[1mSTEP:[0m Checking all the control plane machines are in the expected failure domains [38;5;243m@ 01/31/23 05:59:48.647[0m
INFO: Waiting for the machine deployments to be provisioned
[1mSTEP:[0m Waiting for the workload nodes to exist [38;5;243m@ 01/31/23 05:59:48.672[0m
[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:131 [38;5;243m@ 01/31/23 06:09:48.674[0m
[1mSTEP:[0m Dumping logs from the "md-rollout-4wmdz3" workload cluster [38;5;243m@ 01/31/23 06:09:48.674[0m
Failed to get logs for Machine md-rollout-4wmdz3-d5zbr, Cluster md-rollout-6d5dkh/md-rollout-4wmdz3: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine md-rollout-4wmdz3-md-0-7cb9846cb7-8ksj9, Cluster md-rollout-6d5dkh/md-rollout-4wmdz3: 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-6d5dkh" namespace [38;5;243m@ 01/31/23 06:09:53.634[0m
[1mSTEP:[0m Deleting cluster md-rollout-6d5dkh/md-rollout-4wmdz3 [38;5;243m@ 01/31/23 06:09:53.902[0m
[1mSTEP:[0m Deleting cluster md-rollout-4wmdz3 [38;5;243m@ 01/31/23 06:09:53.921[0m
INFO: Waiting for the Cluster md-rollout-6d5dkh/md-rollout-4wmdz3 to be deleted
[1mSTEP:[0m Waiting for cluster md-rollout-4wmdz3 to be deleted [38;5;243m@ 01/31/23 06:09:53.932[0m
[1mSTEP:[0m Deleting namespace used for hosting the "md-rollout" test spec [38;5;243m@ 01/31/23 06:11:13.977[0m
INFO: Deleting namespace md-rollout-6d5dkh
[38;5;9m• [FAILED] [1196.812 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 600.001s.
Timed out waiting for 1 nodes to be created for MachineDeployment md-rollout-6d5dkh/md-rollout-4wmdz3-md-0
Expected
<int>: 0
to equal
<int>: 1[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:131[0m [38;5;243m@ 01/31/23 06:09:48.674[0m
... skipping 32 lines ...
INFO: Waiting for the cluster infrastructure to be provisioned
[1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/31/23 06:11:15.151[0m
INFO: Waiting for control plane to be initialized
INFO: Waiting for the first control plane machine managed by clusterclass-changes-zw6k3v/clusterclass-changes-kbcsc5-csmpz to be provisioned
[1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/31/23 06:11:35.202[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/31/23 06:21:35.203[0m
[1mSTEP:[0m Dumping logs from the "clusterclass-changes-kbcsc5" workload cluster [38;5;243m@ 01/31/23 06:21:35.203[0m
Failed to get logs for Machine clusterclass-changes-kbcsc5-csmpz-s8jfn, Cluster clusterclass-changes-zw6k3v/clusterclass-changes-kbcsc5: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine clusterclass-changes-kbcsc5-md-0-sbqnb-7956b9fd98-rv5m6, Cluster clusterclass-changes-zw6k3v/clusterclass-changes-kbcsc5: dialing host IP address at : dial tcp :22: connect: connection refused
[1mSTEP:[0m Dumping all the Cluster API resources in the "clusterclass-changes-zw6k3v" namespace [38;5;243m@ 01/31/23 06:21:37.322[0m
[1mSTEP:[0m Deleting cluster clusterclass-changes-zw6k3v/clusterclass-changes-kbcsc5 [38;5;243m@ 01/31/23 06:21:37.606[0m
[1mSTEP:[0m Deleting cluster clusterclass-changes-kbcsc5 [38;5;243m@ 01/31/23 06:21:37.623[0m
INFO: Waiting for the Cluster clusterclass-changes-zw6k3v/clusterclass-changes-kbcsc5 to be deleted
[1mSTEP:[0m Waiting for cluster clusterclass-changes-kbcsc5 to be deleted [38;5;243m@ 01/31/23 06:21:37.639[0m
[1mSTEP:[0m Deleting namespace used for hosting the "clusterclass-changes" test spec [38;5;243m@ 01/31/23 06:21:57.654[0m
INFO: Deleting namespace clusterclass-changes-zw6k3v
[38;5;9m• [FAILED] [643.676 seconds][0m
[0mWhen testing ClusterClass changes [ClusterClass] [38;5;9m[1m[It] Should successfully rollout the managed topology upon changes to the ClusterClass[0m
[38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/clusterclass_changes.go:132[0m
[38;5;9m[FAILED] Timed out after 600.001s.
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/31/23 06:21:35.203[0m
[38;5;243m------------------------------[0m
... skipping 33 lines ...
[1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/31/23 06:21:58.675[0m
INFO: Waiting for control plane to be initialized
INFO: Waiting for the first control plane machine managed by md-scale-g2o70c/md-scale-yjf315 to be provisioned
[1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/31/23 06:22:18.706[0m
[38;5;214m[TIMEDOUT][0m in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/md_scale.go:71 [38;5;243m@ 01/31/23 06:26:29.107[0m
[1mSTEP:[0m Dumping logs from the "md-scale-yjf315" workload cluster [38;5;243m@ 01/31/23 06:26:29.11[0m
Failed to get logs for Machine md-scale-yjf315-5kfdx, Cluster md-scale-g2o70c/md-scale-yjf315: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine md-scale-yjf315-md-0-7b76f6cf99-p4mn4, Cluster md-scale-g2o70c/md-scale-yjf315: 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-g2o70c" namespace [38;5;243m@ 01/31/23 06:26:32.793[0m
[1mSTEP:[0m Deleting cluster md-scale-g2o70c/md-scale-yjf315 [38;5;243m@ 01/31/23 06:26:33.089[0m
[1mSTEP:[0m Deleting cluster md-scale-yjf315 [38;5;243m@ 01/31/23 06:26:33.107[0m
INFO: Waiting for the Cluster md-scale-g2o70c/md-scale-yjf315 to be deleted
[1mSTEP:[0m Waiting for cluster md-scale-yjf315 to be deleted [38;5;243m@ 01/31/23 06:26:33.12[0m
[1mSTEP:[0m Deleting namespace used for hosting the "md-scale" test spec [38;5;243m@ 01/31/23 06:26:53.134[0m
... skipping 84 lines ...
[38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc002286540, 0x27}, {0xc002286570, 0x22}, {0xc0023ab020, 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}}, {{0xc000bdabc0, 0x3a}, {0xc000bdac00, 0x35}, {0xc00150b300, 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}}, {{0xc0010934c0, 0x3e}, {0xc001093500, 0x39}, {0xc0020d0d20, 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;214mgoroutine 25623 [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 25635 [sync.Cond.Wait][0m
... skipping 18 lines ...
[38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc001e3ca20, 0x28}, {0xc001e3ca50, 0x23}, {0xc001ecd514, 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 25549 [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 38721 [chan receive, 4 minutes][0m
... skipping 31 lines ...
[1mSTEP:[0m Cleaning up the vSphere session [38;5;243m@ 01/31/23 06:26:53.159[0m
[1mSTEP:[0m Tearing down the management cluster [38;5;243m@ 01/31/23 06:26:53.372[0m
[38;5;10m[SynchronizedAfterSuite] PASSED [1.572 seconds][0m
[38;5;243m------------------------------[0m
[38;5;9m[1mSummarizing 5 Failures:[0m
[38;5;9m[FAIL][0m [0mWhen testing node drain timeout [38;5;9m[1m[It] A node should be forcefully removed if it cannot be drained in time[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 anti affined nodes [38;5;9m[1m[It] should create a cluster with anti-affined nodes[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:131[0m
[38;5;9m[FAIL][0m [0mWhen testing ClusterClass changes [ClusterClass] [38;5;9m[1m[It] Should successfully rollout the managed topology upon changes to the ClusterClass[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 MachineDeployment scale out/in [38;5;214m[1m[It] Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count[0m
[38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/md_scale.go:71[0m
[38;5;9m[1mRan 5 of 17 Specs in 3573.069 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 (3573.07s)
FAIL
Ginkgo ran 1 suite in 1h0m25.714033287s
Test Suite Failed
real 60m25.733s
user 5m24.228s
sys 1m0.974s
make: *** [Makefile:183: e2e] Error 1
Releasing IP claims
ipclaim.ipam.metal3.io "ip-claim-e72c0e4d0ec73c338a3a798cb59c333c6ed9c2c0" deleted
ipclaim.ipam.metal3.io "workload-ip-claim-aac246deeb953c144b4abf431595aff4a436ed49" 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 ...