periodic-cluster-api-provider-vsphere-conformance-main #1617845616816164864
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 19m44s |
| Revision | main |
... skipping 577 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 11:32:19.817[0m INFO: Waiting for control plane to be initialized INFO: Waiting for the first control plane machine managed by k8s-conformance-yn5yiw/k8s-conformance-pb1ii8 to be provisioned [1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/24/23 11:32:49.855[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 11:42:49.858[0m [1mSTEP:[0m Dumping logs from the "k8s-conformance-pb1ii8" workload cluster [38;5;243m@ 01/24/23 11:42:49.858[0m Failed to get logs for Machine k8s-conformance-pb1ii8-md-0-8c9b788b6-9tlbk, Cluster k8s-conformance-yn5yiw/k8s-conformance-pb1ii8: dialing host IP address at : dial tcp :22: connect: connection refused Failed to get logs for Machine k8s-conformance-pb1ii8-md-0-8c9b788b6-b6zp7, Cluster k8s-conformance-yn5yiw/k8s-conformance-pb1ii8: dialing host IP address at : dial tcp :22: connect: connection refused Failed to get logs for Machine k8s-conformance-pb1ii8-md-0-8c9b788b6-rrfpb, Cluster k8s-conformance-yn5yiw/k8s-conformance-pb1ii8: dialing host IP address at : dial tcp :22: connect: connection refused Failed to get logs for Machine k8s-conformance-pb1ii8-md-0-8c9b788b6-sjn9d, Cluster k8s-conformance-yn5yiw/k8s-conformance-pb1ii8: dialing host IP address at : dial tcp :22: connect: connection refused Failed to get logs for Machine k8s-conformance-pb1ii8-md-0-8c9b788b6-sng8t, Cluster k8s-conformance-yn5yiw/k8s-conformance-pb1ii8: dialing host IP address at : dial tcp :22: connect: connection refused Failed to get logs for Machine k8s-conformance-pb1ii8-x264z, Cluster k8s-conformance-yn5yiw/k8s-conformance-pb1ii8: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 [1mSTEP:[0m Dumping all the Cluster API resources in the "k8s-conformance-yn5yiw" namespace [38;5;243m@ 01/24/23 11:42:52.333[0m [1mSTEP:[0m Deleting cluster k8s-conformance-yn5yiw/k8s-conformance-pb1ii8 [38;5;243m@ 01/24/23 11:42:52.65[0m [1mSTEP:[0m Deleting cluster k8s-conformance-pb1ii8 [38;5;243m@ 01/24/23 11:42:52.666[0m INFO: Waiting for the Cluster k8s-conformance-yn5yiw/k8s-conformance-pb1ii8 to be deleted [1mSTEP:[0m Waiting for cluster k8s-conformance-pb1ii8 to be deleted [38;5;243m@ 01/24/23 11:42:52.68[0m [1mSTEP:[0m Deleting namespace used for hosting the "k8s-conformance" test spec [38;5;243m@ 01/24/23 11:43:12.696[0m INFO: Deleting namespace k8s-conformance-yn5yiw [38;5;9m• [FAILED] [655.405 seconds][0m [0mWhen testing K8S conformance [Conformance] [38;5;9m[1m[It] Should create a workload cluster and run kubetest[0m [38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/k8s_conformance.go:79[0m [38;5;9m[FAILED] Timed out after 600.002s. 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 11:42:49.858[0m [38;5;243m------------------------------[0m ... skipping 2 lines ... [1mSTEP:[0m Cleaning up the vSphere session [38;5;243m@ 01/24/23 11:43:12.716[0m [1mSTEP:[0m Tearing down the management cluster [38;5;243m@ 01/24/23 11:43:12.89[0m [38;5;10m[SynchronizedAfterSuite] PASSED [1.500 seconds][0m [38;5;243m------------------------------[0m [38;5;9m[1mSummarizing 1 Failure:[0m [38;5;9m[FAIL][0m [0mWhen testing K8S conformance [Conformance] [38;5;9m[1m[It] Should create a workload cluster and run kubetest[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[1mRan 1 of 17 Specs in 820.581 seconds[0m [38;5;9m[1mFAIL![0m -- [38;5;10m[1m0 Passed[0m | [38;5;9m[1m1 Failed[0m | [38;5;11m[1m1 Pending[0m | [38;5;14m[1m15 Skipped[0m --- FAIL: TestE2E (820.58s) FAIL Ginkgo ran 1 suite in 15m16.487872371s Test Suite Failed real 15m16.508s user 8m42.785s sys 2m27.501s make: *** [Makefile:183: e2e] Error 1 Releasing IP claims ipclaim.ipam.metal3.io "ip-claim-2f61e3bfbac9efd6793abf744be1e7a85c9373db" deleted ipclaim.ipam.metal3.io "workload-ip-claim-32531ddf9d02b620711549301091b391cdbbb13e" 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 ...