periodic-cluster-api-provider-vsphere-conformance-main #1619657950253551616
Recent runs || View in Spyglass
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 18m23s |
| Revision | main |
... skipping 179 lines ... #18 exporting layers 0.4s done #18 writing image sha256:8a4dae424a496854fc925086be2d6e2a86c11936b09418c09a402a9d31253807 done #18 naming to gcr.io/k8s-staging-cluster-api/capv-manager:e2e done #18 DONE 0.4s #11 [builder 1/6] FROM docker.io/library/golang:1.19.3@sha256:10e3c0f39f8e237baa5b66c5295c578cac42a99536cc9333d8505324a82407d9 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:8a4dae424a496854fc925086be2d6e2a86c11936b09418c09a402a9d31253807 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 the cluster infrastructure to be provisioned [1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/29/23 11:32:42.027[0m INFO: Waiting for control plane to be initialized INFO: Waiting for the first control plane machine managed by k8s-conformance-jjh8rn/k8s-conformance-s1klnf to be provisioned [1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/29/23 11:33:12.073[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/29/23 11:43:12.074[0m [1mSTEP:[0m Dumping logs from the "k8s-conformance-s1klnf" workload cluster [38;5;243m@ 01/29/23 11:43:12.075[0m Failed to get logs for Machine k8s-conformance-s1klnf-md-0-9d696cf56-ffff8, Cluster k8s-conformance-jjh8rn/k8s-conformance-s1klnf: dialing host IP address at : dial tcp :22: connect: connection refused Failed to get logs for Machine k8s-conformance-s1klnf-md-0-9d696cf56-fth8j, Cluster k8s-conformance-jjh8rn/k8s-conformance-s1klnf: dialing host IP address at : dial tcp :22: connect: connection refused Failed to get logs for Machine k8s-conformance-s1klnf-md-0-9d696cf56-gb7wt, Cluster k8s-conformance-jjh8rn/k8s-conformance-s1klnf: dialing host IP address at : dial tcp :22: connect: connection refused Failed to get logs for Machine k8s-conformance-s1klnf-md-0-9d696cf56-m67sw, Cluster k8s-conformance-jjh8rn/k8s-conformance-s1klnf: dialing host IP address at : dial tcp :22: connect: connection refused Failed to get logs for Machine k8s-conformance-s1klnf-md-0-9d696cf56-tp8mc, Cluster k8s-conformance-jjh8rn/k8s-conformance-s1klnf: dialing host IP address at : dial tcp :22: connect: connection refused Failed to get logs for Machine k8s-conformance-s1klnf-n64s9, Cluster k8s-conformance-jjh8rn/k8s-conformance-s1klnf: 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-jjh8rn" namespace [38;5;243m@ 01/29/23 11:43:14.527[0m [1mSTEP:[0m Deleting cluster k8s-conformance-jjh8rn/k8s-conformance-s1klnf [38;5;243m@ 01/29/23 11:43:14.901[0m [1mSTEP:[0m Deleting cluster k8s-conformance-s1klnf [38;5;243m@ 01/29/23 11:43:14.924[0m INFO: Waiting for the Cluster k8s-conformance-jjh8rn/k8s-conformance-s1klnf to be deleted [1mSTEP:[0m Waiting for cluster k8s-conformance-s1klnf to be deleted [38;5;243m@ 01/29/23 11:43:14.938[0m [1mSTEP:[0m Deleting namespace used for hosting the "k8s-conformance" test spec [38;5;243m@ 01/29/23 11:43:24.947[0m INFO: Deleting namespace k8s-conformance-jjh8rn [38;5;9m• [FAILED] [645.785 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. 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/29/23 11:43:12.074[0m [38;5;243m------------------------------[0m ... skipping 4 lines ... [1mSTEP:[0m Cleaning up the vSphere session [38;5;243m@ 01/29/23 11:43:24.969[0m [1mSTEP:[0m Tearing down the management cluster [38;5;243m@ 01/29/23 11:43:25.182[0m [38;5;10m[SynchronizedAfterSuite] PASSED [1.632 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 769.449 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 (769.45s) FAIL Ginkgo ran 1 suite in 13m44.14792853s Test Suite Failed real 13m44.169s user 5m35.642s sys 1m3.406s make: *** [Makefile:183: e2e] Error 1 Releasing IP claims ipclaim.ipam.metal3.io "ip-claim-ccab1c5c4ab38c91c46624a15ff9f28455e0ae45" deleted ipclaim.ipam.metal3.io "workload-ip-claim-9c1bf45ea935ad85bf104b2b4119fc1be850cf07" 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 ...