This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2023-02-02 17:22
Elapsed1h5m
Revisionmain

No Test Failures!

Error lines from build-log.txt

... skipping 173 lines ...
#18 exporting layers
#18 exporting layers 0.4s done
#18 writing image sha256:4241d5dd6417ff875b90a2d4358fed01438250dc64625367f710d60934bb857b
#18 writing image sha256:4241d5dd6417ff875b90a2d4358fed01438250dc64625367f710d60934bb857b 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]                                                
-
- [0 files][ 59.3 MiB/ 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:4241d5dd6417ff875b90a2d4358fed01438250dc64625367f710d60934bb857b 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 266 lines ...
  INFO: Waiting for MachineDeployment rollout for MachineDeploymentTopology "md-0" (class "quick-start-worker") to complete.
  STEP: Deleting a MachineDeploymentTopology in the Cluster Topology and wait for associated MachineDeployment to be deleted @ 02/02/23 17:40:19.995
  INFO: Removing MachineDeploymentTopology from the Cluster Topology.
  INFO: Waiting for MachineDeployment to be deleted.
  STEP: PASSED! @ 02/02/23 17:40:30.111
  STEP: Dumping logs from the "clusterclass-changes-vt0d06" workload cluster @ 02/02/23 17:40:30.112
Failed to get logs for Machine clusterclass-changes-vt0d06-bhtqn-4ptms, Cluster clusterclass-changes-36yc3g/clusterclass-changes-vt0d06: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine clusterclass-changes-vt0d06-md-0-jlhnx-585c96cbcd-pjqtb, Cluster clusterclass-changes-36yc3g/clusterclass-changes-vt0d06: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
  STEP: Dumping all the Cluster API resources in the "clusterclass-changes-36yc3g" namespace @ 02/02/23 17:40:34.475
  STEP: Deleting cluster clusterclass-changes-36yc3g/clusterclass-changes-vt0d06 @ 02/02/23 17:40:34.99
  STEP: Deleting cluster clusterclass-changes-vt0d06 @ 02/02/23 17:40:35.031
  INFO: Waiting for the Cluster clusterclass-changes-36yc3g/clusterclass-changes-vt0d06 to be deleted
  STEP: Waiting for cluster clusterclass-changes-vt0d06 to be deleted @ 02/02/23 17:40:35.049
  STEP: Deleting namespace used for hosting the "clusterclass-changes" test spec @ 02/02/23 17:41:15.092
... skipping 56 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
  STEP: PASSED! @ 02/02/23 17:47:12.354
  STEP: Dumping logs from the "mhc-remediation-jg7gls" workload cluster @ 02/02/23 17:47:12.354
Failed to get logs for Machine mhc-remediation-jg7gls-gzjl9, Cluster mhc-remediation-le3xa7/mhc-remediation-jg7gls: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine mhc-remediation-jg7gls-md-0-849c48fc84-lgmjm, Cluster mhc-remediation-le3xa7/mhc-remediation-jg7gls: 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-le3xa7" namespace @ 02/02/23 17:47:16.854
  STEP: Deleting cluster mhc-remediation-le3xa7/mhc-remediation-jg7gls @ 02/02/23 17:47:17.122
  STEP: Deleting cluster mhc-remediation-jg7gls @ 02/02/23 17:47:17.141
  INFO: Waiting for the Cluster mhc-remediation-le3xa7/mhc-remediation-jg7gls to be deleted
  STEP: Waiting for cluster mhc-remediation-jg7gls to be deleted @ 02/02/23 17:47:17.154
  STEP: Deleting namespace used for hosting the "mhc-remediation" test spec @ 02/02/23 17:47:47.173
... skipping 54 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
  STEP: PASSED! @ 02/02/23 17:58:20.752
  STEP: Dumping logs from the "mhc-remediation-323cnn" workload cluster @ 02/02/23 17:58:20.753
Failed to get logs for Machine mhc-remediation-323cnn-9q9wc, Cluster mhc-remediation-v1ypgr/mhc-remediation-323cnn: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine mhc-remediation-323cnn-b6bh4, Cluster mhc-remediation-v1ypgr/mhc-remediation-323cnn: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine mhc-remediation-323cnn-md-0-86457bd7f8-lvcl2, Cluster mhc-remediation-v1ypgr/mhc-remediation-323cnn: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine mhc-remediation-323cnn-sb9lh, Cluster mhc-remediation-v1ypgr/mhc-remediation-323cnn: 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-v1ypgr" namespace @ 02/02/23 17:58:29.477
  STEP: Deleting cluster mhc-remediation-v1ypgr/mhc-remediation-323cnn @ 02/02/23 17:58:29.779
  STEP: Deleting cluster mhc-remediation-323cnn @ 02/02/23 17:58:29.797
  INFO: Waiting for the Cluster mhc-remediation-v1ypgr/mhc-remediation-323cnn to be deleted
  STEP: Waiting for cluster mhc-remediation-323cnn to be deleted @ 02/02/23 17:58:29.808
  STEP: Deleting namespace used for hosting the "mhc-remediation" test spec @ 02/02/23 17:59:19.838
... skipping 102 lines ...
  INFO: Waiting for the machine deployments to be provisioned
  STEP: Waiting for the workload nodes to exist @ 02/02/23 18:06:40.387
  STEP: Checking all the machines controlled by quick-start-u9h93h-md-0 are in the "<None>" failure domain @ 02/02/23 18:08:20.499
  INFO: Waiting for the machine pools to be provisioned
  STEP: PASSED! @ 02/02/23 18:08:20.538
  STEP: Dumping logs from the "quick-start-u9h93h" workload cluster @ 02/02/23 18:08:20.538
Failed to get logs for Machine quick-start-u9h93h-jdfjg, Cluster quick-start-r4eryl/quick-start-u9h93h: dialing host IP address at 192.168.6.66: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
Failed to get logs for Machine quick-start-u9h93h-md-0-7547df7459-dmwfb, Cluster quick-start-r4eryl/quick-start-u9h93h: dialing host IP address at 192.168.6.119: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
  STEP: Dumping all the Cluster API resources in the "quick-start-r4eryl" namespace @ 02/02/23 18:08:23.308
  STEP: Deleting cluster quick-start-r4eryl/quick-start-u9h93h @ 02/02/23 18:08:23.589
  STEP: Deleting cluster quick-start-u9h93h @ 02/02/23 18:08:23.609
  INFO: Waiting for the Cluster quick-start-r4eryl/quick-start-u9h93h to be deleted
  STEP: Waiting for cluster quick-start-u9h93h to be deleted @ 02/02/23 18:08:23.625
  STEP: Deleting namespace used for hosting the "quick-start" test spec @ 02/02/23 18:08:53.646
... skipping 44 lines ...
  INFO: Waiting for the machine deployments to be provisioned
  STEP: Waiting for the workload nodes to exist @ 02/02/23 18:11:24.992
  STEP: Checking all the machines controlled by quick-start-451od4-md-0-g7mvd are in the "<None>" failure domain @ 02/02/23 18:13:05.107
  INFO: Waiting for the machine pools to be provisioned
  STEP: PASSED! @ 02/02/23 18:13:05.144
  STEP: Dumping logs from the "quick-start-451od4" workload cluster @ 02/02/23 18:13:05.144
Failed to get logs for Machine quick-start-451od4-8v58n-cpcfz, Cluster quick-start-zdke8e/quick-start-451od4: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine quick-start-451od4-md-0-g7mvd-6c4ddf9589-zwcws, Cluster quick-start-zdke8e/quick-start-451od4: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
  STEP: Dumping all the Cluster API resources in the "quick-start-zdke8e" namespace @ 02/02/23 18:13:09.27
  STEP: Deleting cluster quick-start-zdke8e/quick-start-451od4 @ 02/02/23 18:13:09.603
  STEP: Deleting cluster quick-start-451od4 @ 02/02/23 18:13:09.626
  INFO: Waiting for the Cluster quick-start-zdke8e/quick-start-451od4 to be deleted
  STEP: Waiting for cluster quick-start-451od4 to be deleted @ 02/02/23 18:13:09.638
  STEP: Deleting namespace used for hosting the "quick-start" test spec @ 02/02/23 18:13:39.661
... skipping 116 lines ...
  INFO: Waiting for correct number of replicas to exist
  STEP: Scaling the MachineDeployment down to 1 @ 02/02/23 18:26:59.183
  INFO: Scaling machine deployment md-scale-dp14xg/md-scale-k35cwv-md-0 from 3 to 1 replicas
  INFO: Waiting for correct number of replicas to exist
  STEP: PASSED! @ 02/02/23 18:27:09.281
  STEP: Dumping logs from the "md-scale-k35cwv" workload cluster @ 02/02/23 18:27:09.281
Failed to get logs for Machine md-scale-k35cwv-c8gzm, Cluster md-scale-dp14xg/md-scale-k35cwv: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine md-scale-k35cwv-md-0-85fd4cb6-lhz98, Cluster md-scale-dp14xg/md-scale-k35cwv: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
  STEP: Dumping all the Cluster API resources in the "md-scale-dp14xg" namespace @ 02/02/23 18:27:14.058
  STEP: Deleting cluster md-scale-dp14xg/md-scale-k35cwv @ 02/02/23 18:27:14.326
  STEP: Deleting cluster md-scale-k35cwv @ 02/02/23 18:27:14.347
  INFO: Waiting for the Cluster md-scale-dp14xg/md-scale-k35cwv to be deleted
  STEP: Waiting for cluster md-scale-k35cwv to be deleted @ 02/02/23 18:27:14.359
  STEP: Deleting namespace used for hosting the "md-scale" test spec @ 02/02/23 18:27:44.376
... skipping 115 lines ...
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc000dae100, 0x3e}, {0xc000dae140, 0x39}, {0xc00255f020, 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 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 32912 [sync.Cond.Wait]
... skipping 18 lines ...
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc0023eff00, 0x3a}, {0xc0023eff40, 0x35}, {0xc00133a9a0, 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 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 32956 [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 33017 [sync.Cond.Wait]
... skipping 18 lines ...
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc0020ca090, 0x28}, {0xc0020ca0c0, 0x23}, {0xc002733d80, 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 33014 [sync.Cond.Wait]
... skipping 18 lines ...
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc0026ccd80, 0x27}, {0xc0026ccdb0, 0x22}, {0xc002732430, 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 35 lines ...

Summarizing 1 Failure:
  [TIMEDOUT] Cluster Creation using Cluster API quick-start test [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

Ran 9 of 17 Specs in 3490.142 seconds
FAIL! - Suite Timeout Elapsed -- 8 Passed | 1 Failed | 1 Pending | 7 Skipped
--- FAIL: TestE2E (3490.15s)
FAIL

Ginkgo ran 1 suite in 1h0m1.57956795s

Test Suite Failed

real	60m1.614s
user	9m36.899s
sys	2m48.887s
make: *** [Makefile:183: e2e] Error 1
Releasing IP claims
ipclaim.ipam.metal3.io "ip-claim-1b264e2387c5a84b6dd0cfac24b8e24a1e17e727" deleted
ipclaim.ipam.metal3.io "workload-ip-claim-cc69f2338857975158db0d156aabf5e8dfed7143" 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 ...