periodic-cluster-api-provider-vsphere-e2e-main #1617935204087762944 Results

Error lines from build-log.txt

Raw build-log.txt
... skipping 594 lines ...
  Patching MachineHealthCheck unhealthy condition to one of the nodes
  INFO: Patching the node condition to the node
  Waiting for remediation
  Waiting until the node with unhealthy node condition is remediated
  [1mSTEP:[0m PASSED! [38;5;243m@ 01/24/23 17:34:46.632[0m
  [1mSTEP:[0m Dumping logs from the "mhc-remediation-vjmcia" workload cluster [38;5;243m@ 01/24/23 17:34:46.633[0m
Failed to get logs for Machine mhc-remediation-vjmcia-md-0-84c889558b-qjk2d, Cluster mhc-remediation-q4u0kx/mhc-remediation-vjmcia: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine mhc-remediation-vjmcia-t8lk4, Cluster mhc-remediation-q4u0kx/mhc-remediation-vjmcia: 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-q4u0kx" namespace [38;5;243m@ 01/24/23 17:34:51.078[0m
  [1mSTEP:[0m Deleting cluster mhc-remediation-q4u0kx/mhc-remediation-vjmcia [38;5;243m@ 01/24/23 17:34:51.418[0m
  [1mSTEP:[0m Deleting cluster mhc-remediation-vjmcia [38;5;243m@ 01/24/23 17:34:51.44[0m
  INFO: Waiting for the Cluster mhc-remediation-q4u0kx/mhc-remediation-vjmcia to be deleted
  [1mSTEP:[0m Waiting for cluster mhc-remediation-vjmcia to be deleted [38;5;243m@ 01/24/23 17:34:51.455[0m
  [1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 01/24/23 17:35:31.483[0m
... skipping 35 lines ...

  INFO: Waiting for the cluster infrastructure to be provisioned
  [1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/24/23 17:35:32.863[0m
  INFO: Waiting for control plane to be initialized
  INFO: Waiting for the first control plane machine managed by mhc-remediation-oayt9w/mhc-remediation-h7okh2 to be provisioned
  [1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/24/23 17:36:22.914[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/24/23 17:46:22.916[0m
  [1mSTEP:[0m Dumping logs from the "mhc-remediation-h7okh2" workload cluster [38;5;243m@ 01/24/23 17:46:22.916[0m
Failed to get logs for Machine mhc-remediation-h7okh2-46prm, Cluster mhc-remediation-oayt9w/mhc-remediation-h7okh2: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine mhc-remediation-h7okh2-md-0-5f688c776-4jpvc, Cluster mhc-remediation-oayt9w/mhc-remediation-h7okh2: dialing host IP address at : dial tcp :22: connect: connection refused
  [1mSTEP:[0m Dumping all the Cluster API resources in the "mhc-remediation-oayt9w" namespace [38;5;243m@ 01/24/23 17:46:25.152[0m
  [1mSTEP:[0m Deleting cluster mhc-remediation-oayt9w/mhc-remediation-h7okh2 [38;5;243m@ 01/24/23 17:46:25.445[0m
  [1mSTEP:[0m Deleting cluster mhc-remediation-h7okh2 [38;5;243m@ 01/24/23 17:46:25.466[0m
  INFO: Waiting for the Cluster mhc-remediation-oayt9w/mhc-remediation-h7okh2 to be deleted
  [1mSTEP:[0m Waiting for cluster mhc-remediation-h7okh2 to be deleted [38;5;243m@ 01/24/23 17:46:25.479[0m
  [1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 01/24/23 17:46:45.497[0m
  INFO: Deleting namespace mhc-remediation-oayt9w
[38;5;9m• [FAILED] [674.013 seconds][0m
[0mWhen testing unhealthy machines remediation [38;5;9m[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[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/24/23 17:46:22.916[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/24/23 17:46:46.689[0m
  INFO: Waiting for control plane to be initialized
  INFO: Waiting for the first control plane machine managed by md-scale-f82pcd/md-scale-uclkot to be provisioned
  [1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/24/23 17:47:36.741[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/24/23 17:57:36.742[0m
  [1mSTEP:[0m Dumping logs from the "md-scale-uclkot" workload cluster [38;5;243m@ 01/24/23 17:57:36.742[0m
Failed to get logs for Machine md-scale-uclkot-5vk9q, Cluster md-scale-f82pcd/md-scale-uclkot: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine md-scale-uclkot-md-0-69cf748df9-9svld, Cluster md-scale-f82pcd/md-scale-uclkot: dialing host IP address at : dial tcp :22: connect: connection refused
  [1mSTEP:[0m Dumping all the Cluster API resources in the "md-scale-f82pcd" namespace [38;5;243m@ 01/24/23 17:57:39.033[0m
  [1mSTEP:[0m Deleting cluster md-scale-f82pcd/md-scale-uclkot [38;5;243m@ 01/24/23 17:57:39.328[0m
  [1mSTEP:[0m Deleting cluster md-scale-uclkot [38;5;243m@ 01/24/23 17:57:39.346[0m
  INFO: Waiting for the Cluster md-scale-f82pcd/md-scale-uclkot to be deleted
  [1mSTEP:[0m Waiting for cluster md-scale-uclkot to be deleted [38;5;243m@ 01/24/23 17:57:39.365[0m
  [1mSTEP:[0m Deleting namespace used for hosting the "md-scale" test spec [38;5;243m@ 01/24/23 17:57:59.38[0m
  INFO: Deleting namespace md-scale-f82pcd
[38;5;9m• [FAILED] [673.886 seconds][0m
[0mWhen testing MachineDeployment scale out/in [38;5;9m[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[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/24/23 17:57:36.742[0m
[38;5;243m------------------------------[0m
... skipping 33 lines ...

  INFO: Waiting for the cluster infrastructure to be provisioned
  [1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/24/23 17:58:00.586[0m
  INFO: Waiting for control plane to be initialized
  INFO: Waiting for the first control plane machine managed by dhcp-overrides-wlc1ts/dhcp-overrides-fx84w5 to be provisioned
  [1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/24/23 17:58:50.643[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/24/23 18:08:50.645[0m
  [1mSTEP:[0m Dumping all the Cluster API resources in the "dhcp-overrides-wlc1ts" namespace [38;5;243m@ 01/24/23 18:08:50.645[0m
  [1mSTEP:[0m cleaning up namespace: dhcp-overrides-wlc1ts [38;5;243m@ 01/24/23 18:08:50.95[0m
  [1mSTEP:[0m Deleting cluster dhcp-overrides-fx84w5 [38;5;243m@ 01/24/23 18:08:50.97[0m
  INFO: Waiting for the Cluster dhcp-overrides-wlc1ts/dhcp-overrides-fx84w5 to be deleted
  [1mSTEP:[0m Waiting for cluster dhcp-overrides-fx84w5 to be deleted [38;5;243m@ 01/24/23 18:08:50.984[0m
  [1mSTEP:[0m Deleting namespace used for hosting test spec [38;5;243m@ 01/24/23 18:09:10.999[0m
  INFO: Deleting namespace dhcp-overrides-wlc1ts
[38;5;9m• [FAILED] [671.621 seconds][0m
[0mDHCPOverrides configuration test [38;5;243mwhen Creating a cluster with DHCPOverrides configured [38;5;9m[1m[It] Only configures the network with the provided nameservers[0m
[38;5;243m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-vsphere/test/e2e/dhcp_overrides_test.go:66[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/24/23 18:08:50.645[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/24/23 18:09:12.175[0m
  INFO: Waiting for control plane to be initialized
  INFO: Waiting for the first control plane machine managed by quick-start-yfeifn/quick-start-4c2hsl to be provisioned
  [1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/24/23 18:09:32.216[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/24/23 18:19:32.219[0m
  [1mSTEP:[0m Dumping logs from the "quick-start-4c2hsl" workload cluster [38;5;243m@ 01/24/23 18:19:32.22[0m
Failed to get logs for Machine quick-start-4c2hsl-md-0-d7f7c8845-8xx4j, Cluster quick-start-yfeifn/quick-start-4c2hsl: dialing host IP address at : dial tcp :22: connect: connection refused
Failed to get logs for Machine quick-start-4c2hsl-p6mvf, Cluster quick-start-yfeifn/quick-start-4c2hsl: dialing host IP address at 192.168.6.151: 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-yfeifn" namespace [38;5;243m@ 01/24/23 18:19:33.558[0m
  [1mSTEP:[0m Deleting cluster quick-start-yfeifn/quick-start-4c2hsl [38;5;243m@ 01/24/23 18:19:33.86[0m
  [1mSTEP:[0m Deleting cluster quick-start-4c2hsl [38;5;243m@ 01/24/23 18:19:33.88[0m
  INFO: Waiting for the Cluster quick-start-yfeifn/quick-start-4c2hsl to be deleted
  [1mSTEP:[0m Waiting for cluster quick-start-4c2hsl to be deleted [38;5;243m@ 01/24/23 18:19:33.895[0m
  [1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 01/24/23 18:19:53.91[0m
  INFO: Deleting namespace quick-start-yfeifn
[38;5;9m• [FAILED] [642.907 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.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/24/23 18:19:32.219[0m
[38;5;243m------------------------------[0m
... skipping 33 lines ...
  [1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/24/23 18:19:55.134[0m
  INFO: Waiting for control plane to be initialized
  INFO: Waiting for the first control plane machine managed by quick-start-5garco/quick-start-rdun14-r9tlq to be provisioned
  [1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/24/23 18:20:15.197[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@ 01/24/23 18:24:06.7[0m
  [1mSTEP:[0m Dumping logs from the "quick-start-rdun14" workload cluster [38;5;243m@ 01/24/23 18:24:06.702[0m
Failed to get logs for Machine quick-start-rdun14-md-0-x6x6m-687c7479d9-6rfbn, Cluster quick-start-5garco/quick-start-rdun14: dialing host IP address at : dial tcp :22: connect: connection refused
Failed to get logs for Machine quick-start-rdun14-r9tlq-bmqvt, Cluster quick-start-5garco/quick-start-rdun14: 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-5garco" namespace [38;5;243m@ 01/24/23 18:24:08.843[0m
  [1mSTEP:[0m Deleting cluster quick-start-5garco/quick-start-rdun14 [38;5;243m@ 01/24/23 18:24:09.152[0m
  [1mSTEP:[0m Deleting cluster quick-start-rdun14 [38;5;243m@ 01/24/23 18:24:09.177[0m
  INFO: Waiting for the Cluster quick-start-5garco/quick-start-rdun14 to be deleted
  [1mSTEP:[0m Waiting for cluster quick-start-rdun14 to be deleted [38;5;243m@ 01/24/23 18:24:09.193[0m
  [1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 01/24/23 18:24:29.212[0m
... skipping 84 lines ...
        [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc0015aee00, 0x3a}, {0xc0015aee40, 0x35}, {0xc0015aabc0, 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}}, {{0xc000b78680, 0x3e}, {0xc000b786c0, 0x39}, {0xc002173bf0, 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 21 lines ...
        [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc0022dd5c0, 0x27}, {0xc0022dd5f0, 0x22}, {0xc00202ddd4, 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 44 lines ...
        [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc0020ab620, 0x28}, {0xc0020ab650, 0x23}, {0xc002bad790, 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 33323 [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 33346 [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 33260 [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;243m------------------------------[0m
[38;5;14mS[0m
... skipping 8 lines ...
  [1mSTEP:[0m Cleaning up the vSphere session [38;5;243m@ 01/24/23 18:24:29.232[0m
  [1mSTEP:[0m Tearing down the management cluster [38;5;243m@ 01/24/23 18:24:29.452[0m
[38;5;10m[SynchronizedAfterSuite] PASSED [1.533 seconds][0m
[38;5;243m------------------------------[0m

[38;5;9m[1mSummarizing 5 Failures:[0m
  [38;5;9m[FAIL][0m [0mWhen testing unhealthy machines remediation [38;5;9m[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/framework/controlplane_helpers.go:154[0m
  [38;5;9m[FAIL][0m [0mWhen testing MachineDeployment scale out/in [38;5;9m[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/framework/controlplane_helpers.go:154[0m
  [38;5;9m[FAIL][0m [0mDHCPOverrides configuration test [38;5;243mwhen Creating a cluster with DHCPOverrides configured [38;5;9m[1m[It] Only configures the network with the provided nameservers[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 [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;214m[TIMEDOUT][0m [0mClusterClass Creation using Cluster API quick-start test [PR-Blocking] [ClusterClass] [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 6 of 17 Specs in 3569.230 seconds[0m
[38;5;9m[1mFAIL! - Suite Timeout Elapsed[0m -- [38;5;10m[1m1 Passed[0m | [38;5;9m[1m5 Failed[0m | [38;5;11m[1m1 Pending[0m | [38;5;14m[1m10 Skipped[0m
--- FAIL: TestE2E (3569.23s)
FAIL

Ginkgo ran 1 suite in 1h0m24.181139279s

Test Suite Failed

real	60m24.208s
user	5m46.247s
sys	1m9.742s
make: *** [Makefile:183: e2e] Error 1
Releasing IP claims
ipclaim.ipam.metal3.io "ip-claim-7cefa2ef5d01a99049414a9d1258a5c700549056" deleted
ipclaim.ipam.metal3.io "workload-ip-claim-da659fd3b57d3ad3eef0634a2968711bd1d6830f" 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 ...
Result	FAILURE
Tests	0 failed / 0 succeeded
Started	2023-01-24 17:19
Elapsed	1h5m
Revision	main
periodic-cluster-api-provider-vsphere-e2e-main #1617935204087762944

No Test Failures!

Error lines from build-log.txt
