periodic-cluster-api-provider-vsphere-conformance-main #1617120569612832768
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 28m52s |
| Revision | main |
... skipping 578 lines ... INFO: Waiting for control plane to be ready INFO: Waiting for control plane k8s-conformance-43i3p4/k8s-conformance-o09x4g 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/22/23 11:32:42.393[0m [1mSTEP:[0m Checking all the control plane machines are in the expected failure domains [38;5;243m@ 01/22/23 11:40:32.704[0m INFO: Waiting for the machine deployments to be provisioned [1mSTEP:[0m Waiting for the workload nodes to exist [38;5;243m@ 01/22/23 11:40:32.73[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/22/23 11:50:32.731[0m [1mSTEP:[0m Dumping logs from the "k8s-conformance-o09x4g" workload cluster [38;5;243m@ 01/22/23 11:50:32.731[0m Failed to get logs for Machine k8s-conformance-o09x4g-6wfsx, Cluster k8s-conformance-43i3p4/k8s-conformance-o09x4g: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine k8s-conformance-o09x4g-md-0-876f876cb-b7x4j, Cluster k8s-conformance-43i3p4/k8s-conformance-o09x4g: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine k8s-conformance-o09x4g-md-0-876f876cb-fg2r9, Cluster k8s-conformance-43i3p4/k8s-conformance-o09x4g: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine k8s-conformance-o09x4g-md-0-876f876cb-jdz4d, Cluster k8s-conformance-43i3p4/k8s-conformance-o09x4g: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine k8s-conformance-o09x4g-md-0-876f876cb-k6jpq, Cluster k8s-conformance-43i3p4/k8s-conformance-o09x4g: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine k8s-conformance-o09x4g-md-0-876f876cb-tw8hf, Cluster k8s-conformance-43i3p4/k8s-conformance-o09x4g: 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-43i3p4" namespace [38;5;243m@ 01/22/23 11:50:45.054[0m [1mSTEP:[0m Deleting cluster k8s-conformance-43i3p4/k8s-conformance-o09x4g [38;5;243m@ 01/22/23 11:50:45.444[0m [1mSTEP:[0m Deleting cluster k8s-conformance-o09x4g [38;5;243m@ 01/22/23 11:50:45.461[0m INFO: Waiting for the Cluster k8s-conformance-43i3p4/k8s-conformance-o09x4g to be deleted [1mSTEP:[0m Waiting for cluster k8s-conformance-o09x4g to be deleted [38;5;243m@ 01/22/23 11:50:45.477[0m [1mSTEP:[0m Deleting namespace used for hosting the "k8s-conformance" test spec [38;5;243m@ 01/22/23 11:51:15.496[0m INFO: Deleting namespace k8s-conformance-43i3p4 [38;5;9m• [FAILED] [1285.759 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.000s. Timed out waiting for 5 nodes to be created for MachineDeployment k8s-conformance-43i3p4/k8s-conformance-o09x4g-md-0 Expected <int>: 4 to equal <int>: 5[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/22/23 11:50:32.731[0m ... skipping 10 lines ... [1mSTEP:[0m Cleaning up the vSphere session [38;5;243m@ 01/22/23 11:51:15.52[0m [1mSTEP:[0m Tearing down the management cluster [38;5;243m@ 01/22/23 11:51:15.729[0m [38;5;10m[SynchronizedAfterSuite] PASSED [2.095 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/machinedeployment_helpers.go:131[0m [38;5;9m[1mRan 1 of 17 Specs in 1406.272 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 (1406.27s) FAIL Ginkgo ran 1 suite in 24m18.959021921s Test Suite Failed real 24m18.985s user 5m19.897s sys 1m0.889s make: *** [Makefile:183: e2e] Error 1 Releasing IP claims ipclaim.ipam.metal3.io "ip-claim-01017801a2d11bc6c7fa764671f78864afefaff2" deleted ipclaim.ipam.metal3.io "workload-ip-claim-dd2508b76b2a29ea1e8898f029dd1cef91fd0e7d" 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 ...