This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2023-01-24 05:19
Elapsed1h4m
Revisionmain

No Test Failures!


Error lines from build-log.txt

... skipping 173 lines ...
#18 exporting to image
#18 exporting layers
#18 exporting layers 0.4s done
#18 writing image sha256:c0db9accf803e92033821b9b3e33ebfe08e6145fae13b389234d88ee7962654b 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 126 lines ...

#18 exporting to image
#18 exporting layers done
#18 writing image sha256:c0db9accf803e92033821b9b3e33ebfe08e6145fae13b389234d88ee7962654b 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 250 lines ...
  INFO: Waiting for control plane to be ready
  INFO: Waiting for control plane mhc-remediation-vo6bdk/mhc-remediation-2ge90n to be ready (implies underlying nodes to be ready as well)
  STEP: Waiting for the control plane to be ready @ 01/24/23 05:29:59.297
  STEP: Checking all the control plane machines are in the expected failure domains @ 01/24/23 05:30:49.337
  INFO: Waiting for the machine deployments to be provisioned
  STEP: Waiting for the workload nodes to exist @ 01/24/23 05:30:49.361
  [FAILED] in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/machinedeployment_helpers.go:131 @ 01/24/23 05:40:49.362
  STEP: Dumping logs from the "mhc-remediation-2ge90n" workload cluster @ 01/24/23 05:40:49.362
Failed to get logs for Machine mhc-remediation-2ge90n-md-0-84679c7d7-b6pdx, Cluster mhc-remediation-vo6bdk/mhc-remediation-2ge90n: dialing host IP address at : dial tcp :22: connect: connection refused
Failed to get logs for Machine mhc-remediation-2ge90n-rsmmf, Cluster mhc-remediation-vo6bdk/mhc-remediation-2ge90n: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
  STEP: Dumping all the Cluster API resources in the "mhc-remediation-vo6bdk" namespace @ 01/24/23 05:40:51.67
  STEP: Deleting cluster mhc-remediation-vo6bdk/mhc-remediation-2ge90n @ 01/24/23 05:40:51.969
  STEP: Deleting cluster mhc-remediation-2ge90n @ 01/24/23 05:40:51.99
  INFO: Waiting for the Cluster mhc-remediation-vo6bdk/mhc-remediation-2ge90n to be deleted
  STEP: Waiting for cluster mhc-remediation-2ge90n to be deleted @ 01/24/23 05:40:52.004
  STEP: Deleting namespace used for hosting the "mhc-remediation" test spec @ 01/24/23 05:41:22.028
  INFO: Deleting namespace mhc-remediation-vo6bdk
• [FAILED] [875.480 seconds]
When testing unhealthy machines remediation [It] Should successfully trigger machine deployment remediation
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/mhc_remediations.go:83

  [FAILED] Timed out after 600.000s.
  Timed out waiting for 1 nodes to be created for MachineDeployment mhc-remediation-vo6bdk/mhc-remediation-2ge90n-md-0
  Expected
      <int>: 0
  to equal
      <int>: 1
  In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/machinedeployment_helpers.go:131 @ 01/24/23 05:40:49.362
... skipping 33 lines ...

  INFO: Waiting for the cluster infrastructure to be provisioned
  STEP: Waiting for cluster to enter the provisioned phase @ 01/24/23 05:41:23.208
  INFO: Waiting for control plane to be initialized
  INFO: Waiting for the first control plane machine managed by mhc-remediation-tqgfph/mhc-remediation-asn76m to be provisioned
  STEP: Waiting for one control plane node to exist @ 01/24/23 05:42:13.261
  [FAILED] in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154 @ 01/24/23 05:52:13.263
  STEP: Dumping logs from the "mhc-remediation-asn76m" workload cluster @ 01/24/23 05:52:13.264
Failed to get logs for Machine mhc-remediation-asn76m-md-0-65fd5757cf-m6j9x, Cluster mhc-remediation-tqgfph/mhc-remediation-asn76m: dialing host IP address at : dial tcp :22: connect: connection refused
Failed to get logs for Machine mhc-remediation-asn76m-sbvcj, Cluster mhc-remediation-tqgfph/mhc-remediation-asn76m: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
  STEP: Dumping all the Cluster API resources in the "mhc-remediation-tqgfph" namespace @ 01/24/23 05:52:15.565
  STEP: Deleting cluster mhc-remediation-tqgfph/mhc-remediation-asn76m @ 01/24/23 05:52:15.833
  STEP: Deleting cluster mhc-remediation-asn76m @ 01/24/23 05:52:15.851
  INFO: Waiting for the Cluster mhc-remediation-tqgfph/mhc-remediation-asn76m to be deleted
  STEP: Waiting for cluster mhc-remediation-asn76m to be deleted @ 01/24/23 05:52:15.864
  STEP: Deleting namespace used for hosting the "mhc-remediation" test spec @ 01/24/23 05:52:35.881
  INFO: Deleting namespace mhc-remediation-tqgfph
• [FAILED] [673.853 seconds]
When testing unhealthy machines remediation [It] Should successfully trigger KCP remediation
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/mhc_remediations.go:116

  [FAILED] Timed out after 600.001s.
  No Control Plane machines came into existence. 
  Expected
      <bool>: false
  to be true
  In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154 @ 01/24/23 05:52:13.263
------------------------------
... skipping 31 lines ...

  INFO: Waiting for the cluster infrastructure to be provisioned
  STEP: Waiting for cluster to enter the provisioned phase @ 01/24/23 05:52:37.075
  INFO: Waiting for control plane to be initialized
  INFO: Waiting for the first control plane machine managed by quick-start-70vw8c/quick-start-oanfw1 to be provisioned
  STEP: Waiting for one control plane node to exist @ 01/24/23 05:52:57.108
  [FAILED] in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154 @ 01/24/23 06:02:57.109
  STEP: Dumping logs from the "quick-start-oanfw1" workload cluster @ 01/24/23 06:02:57.109
Failed to get logs for Machine quick-start-oanfw1-bd2bp, Cluster quick-start-70vw8c/quick-start-oanfw1: dialing host IP address at 192.168.6.79: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
Failed to get logs for Machine quick-start-oanfw1-md-0-f4bcd5945-csfmp, Cluster quick-start-70vw8c/quick-start-oanfw1: dialing host IP address at : dial tcp :22: connect: connection refused
  STEP: Dumping all the Cluster API resources in the "quick-start-70vw8c" namespace @ 01/24/23 06:02:58.147
  STEP: Deleting cluster quick-start-70vw8c/quick-start-oanfw1 @ 01/24/23 06:02:58.437
  STEP: Deleting cluster quick-start-oanfw1 @ 01/24/23 06:02:58.457
  INFO: Waiting for the Cluster quick-start-70vw8c/quick-start-oanfw1 to be deleted
  STEP: Waiting for cluster quick-start-oanfw1 to be deleted @ 01/24/23 06:02:58.473
  [FAILED] in [AfterEach] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/cluster_helpers.go:176 @ 01/24/23 06:07:58.475
• [FAILED] [922.575 seconds]
Cluster creation with [Ignition] bootstrap [PR-Blocking] [It] Should create a workload cluster
/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/quick_start.go:78

  [FAILED] Timed out after 600.000s.
  No Control Plane machines came into existence. 
  Expected
      <bool>: false
  to be true
  In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154 @ 01/24/23 06:02:57.109

... skipping 33 lines ...

  INFO: Waiting for the cluster infrastructure to be provisioned
  STEP: Waiting for cluster to enter the provisioned phase @ 01/24/23 06:07:59.587
  INFO: Waiting for control plane to be initialized
  INFO: Waiting for the first control plane machine managed by anti-affinity-e2e-jk8m0z/anti-affinity-t5wtsq to be provisioned
  STEP: Waiting for one control plane node to exist @ 01/24/23 06:08:49.634
  [FAILED] in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154 @ 01/24/23 06:18:49.635
  STEP: Dumping all the Cluster API resources in the "anti-affinity-e2e-jk8m0z" namespace @ 01/24/23 06:18:49.635
  STEP: cleaning up namespace: anti-affinity-e2e-jk8m0z @ 01/24/23 06:18:49.95
  STEP: Deleting cluster anti-affinity-t5wtsq @ 01/24/23 06:18:49.989
  INFO: Waiting for the Cluster anti-affinity-e2e-jk8m0z/anti-affinity-t5wtsq to be deleted
  STEP: Waiting for cluster anti-affinity-t5wtsq to be deleted @ 01/24/23 06:18:50.036
  STEP: Deleting namespace used for hosting test spec @ 01/24/23 06:19:10.052
  INFO: Deleting namespace anti-affinity-e2e-jk8m0z
• [FAILED] [671.600 seconds]
Cluster creation with anti affined nodes [It] should create a cluster with anti-affined nodes
/home/prow/go/src/sigs.k8s.io/cluster-api-provider-vsphere/test/e2e/anti_affinity_test.go:61

  [FAILED] Timed out after 600.000s.
  No Control Plane machines came into existence. 
  Expected
      <bool>: false
  to be true
  In [It] at: /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154 @ 01/24/23 06:18:49.635
------------------------------
... skipping 135 lines ...
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc002619e80, 0x3a}, {0xc002619ec0, 0x35}, {0xc00157f700, 0x1d}, ...}, ...}, ...)
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186
              | out := bufio.NewWriter(f)
              | defer out.Flush()
              > _, err = out.ReadFrom(podLogs)
              | if err != nil && err != io.ErrUnexpectedEOF {
              | 	// Failing to stream logs should not cause the test to fail
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161
              | 
              | // Watch each container's logs in a goroutine so we can stream them all concurrently.
              > go func(pod corev1.Pod, container corev1.Container) {
              | 	defer GinkgoRecover()
... skipping 29 lines ...
              | for {
              > 	select {
              | 	case <-ctx.Done():
              | 		return
        > sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225
              | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment))
              | 
              > go func() {
              | 	defer GinkgoRecover()
              | 	for {

        goroutine 33503 [select]
... skipping 3 lines ...
              | for {
              > 	select {
              | 	case <-ctx.Done():
              | 		return
        > sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225
              | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment))
              | 
              > go func() {
              | 	defer GinkgoRecover()
              | 	for {

        goroutine 33522 [sync.Cond.Wait]
... skipping 18 lines ...
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc0029c8390, 0x28}, {0xc0029c83c0, 0x23}, {0xc00227b144, 0xb}, ...}, ...}, ...)
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186
              | out := bufio.NewWriter(f)
              | defer out.Flush()
              > _, err = out.ReadFrom(podLogs)
              | if err != nil && err != io.ErrUnexpectedEOF {
              | 	// Failing to stream logs should not cause the test to fail
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161
              | 
              | // Watch each container's logs in a goroutine so we can stream them all concurrently.
              > go func(pod corev1.Pod, container corev1.Container) {
              | 	defer GinkgoRecover()
... skipping 44 lines ...
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc001543a40, 0x3e}, {0xc001543a80, 0x39}, {0xc0026640c0, 0x21}, ...}, ...}, ...)
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186
              | out := bufio.NewWriter(f)
              | defer out.Flush()
              > _, err = out.ReadFrom(podLogs)
              | if err != nil && err != io.ErrUnexpectedEOF {
              | 	// Failing to stream logs should not cause the test to fail
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161
              | 
              | // Watch each container's logs in a goroutine so we can stream them all concurrently.
              > go func(pod corev1.Pod, container corev1.Container) {
              | 	defer GinkgoRecover()
... skipping 21 lines ...
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc002244990, 0x27}, {0xc0022449c0, 0x22}, {0xc0022076a0, 0xb}, ...}, ...}, ...)
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186
              | out := bufio.NewWriter(f)
              | defer out.Flush()
              > _, err = out.ReadFrom(podLogs)
              | if err != nil && err != io.ErrUnexpectedEOF {
              | 	// Failing to stream logs should not cause the test to fail
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161
              | 
              | // Watch each container's logs in a goroutine so we can stream them all concurrently.
              > go func(pod corev1.Pod, container corev1.Container) {
              | 	defer GinkgoRecover()
... skipping 6 lines ...
              | for {
              > 	select {
              | 	case <-ctx.Done():
              | 		return
        > sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225
              | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment))
              | 
              > go func() {
              | 	defer GinkgoRecover()
              | 	for {

        goroutine 33524 [select]
... skipping 3 lines ...
              | for {
              > 	select {
              | 	case <-ctx.Done():
              | 		return
        > sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225
              | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment))
              | 
              > go func() {
              | 	defer GinkgoRecover()
              | 	for {
------------------------------
SSSS
... skipping 8 lines ...
  STEP: Cleaning up the vSphere session @ 01/24/23 06:24:15.859
  STEP: Tearing down the management cluster @ 01/24/23 06:24:16.065
[SynchronizedAfterSuite] PASSED [1.569 seconds]
------------------------------

Summarizing 5 Failures:
  [FAIL] When testing unhealthy machines remediation [It] Should successfully trigger machine deployment remediation
  /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/machinedeployment_helpers.go:131
  [FAIL] When testing unhealthy machines remediation [It] Should successfully trigger KCP remediation
  /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154
  [FAIL] Cluster creation with [Ignition] bootstrap [PR-Blocking] [It] Should create a workload cluster
  /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154
  [FAIL] Cluster creation with anti affined nodes [It] should create a cluster with anti-affined nodes
  /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:154
  [TIMEDOUT] Label nodes with ESXi host info [It] creates a workload cluster whose nodes have the ESXi host info
  /home/prow/go/src/sigs.k8s.io/cluster-api-provider-vsphere/test/e2e/node_labeling_test.go:52

Ran 5 of 17 Specs in 3568.115 seconds
FAIL! - Suite Timeout Elapsed -- 0 Passed | 5 Failed | 1 Pending | 11 Skipped
--- FAIL: TestE2E (3568.12s)
FAIL

Ginkgo ran 1 suite in 1h0m22.019155799s

Test Suite Failed

real	60m22.040s
user	5m38.779s
sys	1m5.137s
make: *** [Makefile:183: e2e] Error 1
Releasing IP claims
ipclaim.ipam.metal3.io "ip-claim-3683430e580e28cdfb70fd6e2e9d4eebba02a10d" deleted
ipclaim.ipam.metal3.io "workload-ip-claim-23b778a68c65ae01da3bd9d7672f071439a6bce3" 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 ...