periodic-cluster-api-provider-vsphere-e2e-main #1619747541497155584
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 1h4m |
| Revision | main |
... skipping 171 lines ... #18 exporting to image #18 exporting layers #18 exporting layers 0.4s done #18 writing image sha256:d6c0610dbbbc0c4d15d1c8afb0ce7501c696f2d3909a2f675ac8cc7388dc1680 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][ 72.7 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 129 lines ... #18 exporting to image #18 exporting layers done #18 writing image sha256:d6c0610dbbbc0c4d15d1c8afb0ce7501c696f2d3909a2f675ac8cc7388dc1680 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 243 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 17:28:31.871[0m INFO: Waiting for control plane to be initialized INFO: Waiting for the first control plane machine managed by node-labeling-e2e-65gmuw/node-labeling-5a3sei to be provisioned [1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/29/23 17:29:01.914[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 17:39:01.917[0m [1mSTEP:[0m Dumping all the Cluster API resources in the "node-labeling-e2e-65gmuw" namespace [38;5;243m@ 01/29/23 17:39:01.917[0m [1mSTEP:[0m cleaning up namespace: node-labeling-e2e-65gmuw [38;5;243m@ 01/29/23 17:39:02.238[0m [1mSTEP:[0m Deleting cluster node-labeling-5a3sei [38;5;243m@ 01/29/23 17:39:02.257[0m INFO: Waiting for the Cluster node-labeling-e2e-65gmuw/node-labeling-5a3sei to be deleted [1mSTEP:[0m Waiting for cluster node-labeling-5a3sei to be deleted [38;5;243m@ 01/29/23 17:39:02.27[0m [1mSTEP:[0m Deleting namespace used for hosting test spec [38;5;243m@ 01/29/23 17:39:22.287[0m INFO: Deleting namespace node-labeling-e2e-65gmuw [38;5;9m• [FAILED] [652.949 seconds][0m [0mLabel nodes with ESXi host info [38;5;9m[1m[It] creates a workload cluster whose nodes have the ESXi host info[0m [38;5;243m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-vsphere/test/e2e/node_labeling_test.go:52[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/29/23 17:39:01.917[0m [38;5;243m------------------------------[0m ... skipping 31 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 17:39:23.563[0m INFO: Waiting for control plane to be initialized INFO: Waiting for the first control plane machine managed by capv-e2e-79vj0u/storage-policy-02sapx to be provisioned [1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/29/23 17:40:13.622[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 17:50:13.625[0m [1mSTEP:[0m Dumping all the Cluster API resources in the "capv-e2e-79vj0u" namespace [38;5;243m@ 01/29/23 17:50:13.625[0m [1mSTEP:[0m cleaning up namespace: capv-e2e-79vj0u [38;5;243m@ 01/29/23 17:50:13.944[0m [1mSTEP:[0m Deleting cluster storage-policy-02sapx [38;5;243m@ 01/29/23 17:50:13.964[0m INFO: Waiting for the Cluster capv-e2e-79vj0u/storage-policy-02sapx to be deleted [1mSTEP:[0m Waiting for cluster storage-policy-02sapx to be deleted [38;5;243m@ 01/29/23 17:50:13.978[0m [1mSTEP:[0m Deleting namespace used for hosting test spec [38;5;243m@ 01/29/23 17:50:23.988[0m INFO: Deleting namespace capv-e2e-79vj0u [38;5;9m• [FAILED] [661.702 seconds][0m [0mCluster creation with storage policy [38;5;9m[1m[It] should create a cluster successfully[0m [38;5;243m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-vsphere/test/e2e/storage_policy_test.go:57[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/29/23 17:50:13.625[0m [38;5;243m------------------------------[0m ... skipping 34 lines ... INFO: Waiting for control plane to be initialized INFO: Waiting for the first control plane machine managed by quick-start-x84sxu/quick-start-2ab8hv to be provisioned [1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/29/23 17:51:15.197[0m INFO: Waiting for control plane to be ready INFO: Waiting for control plane quick-start-x84sxu/quick-start-2ab8hv 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/29/23 17:55:35.39[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:176 [38;5;243m@ 01/29/23 18:05:35.392[0m [1mSTEP:[0m Dumping logs from the "quick-start-2ab8hv" workload cluster [38;5;243m@ 01/29/23 18:05:35.392[0m Failed to get logs for Machine quick-start-2ab8hv-bdp9j, Cluster quick-start-x84sxu/quick-start-2ab8hv: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine quick-start-2ab8hv-md-0-787c6dfff6-8fhxh, Cluster quick-start-x84sxu/quick-start-2ab8hv: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 [1mSTEP:[0m Dumping all the Cluster API resources in the "quick-start-x84sxu" namespace [38;5;243m@ 01/29/23 18:05:39.605[0m [1mSTEP:[0m Deleting cluster quick-start-x84sxu/quick-start-2ab8hv [38;5;243m@ 01/29/23 18:05:39.905[0m [1mSTEP:[0m Deleting cluster quick-start-2ab8hv [38;5;243m@ 01/29/23 18:05:39.926[0m INFO: Waiting for the Cluster quick-start-x84sxu/quick-start-2ab8hv to be deleted [1mSTEP:[0m Waiting for cluster quick-start-2ab8hv to be deleted [38;5;243m@ 01/29/23 18:05:39.941[0m [1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 01/29/23 18:05:59.958[0m INFO: Deleting namespace quick-start-x84sxu [38;5;9m• [FAILED] [935.965 seconds][0m [0mCluster Creation using Cluster API quick-start test [PR-Blocking] [38;5;9m[1m[It] Should create a workload cluster[0m [38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/quick_start.go:78[0m [38;5;9m[FAILED] Timed out after 600.001s. { "metadata": { "creationTimestamp": null }, "spec": { "version": "", ... skipping 64 lines ... INFO: Waiting for control plane to be ready INFO: Waiting for control plane md-rollout-t3zvld/md-rollout-pf4k1h 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/29/23 18:15:31.509[0m [1mSTEP:[0m Checking all the control plane machines are in the expected failure domains [38;5;243m@ 01/29/23 18:15:31.516[0m INFO: Waiting for the machine deployments to be provisioned [1mSTEP:[0m Waiting for the workload nodes to exist [38;5;243m@ 01/29/23 18:15:31.55[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/29/23 18:25:31.551[0m [1mSTEP:[0m Dumping logs from the "md-rollout-pf4k1h" workload cluster [38;5;243m@ 01/29/23 18:25:31.551[0m Failed to get logs for Machine md-rollout-pf4k1h-md-0-95c47ffd-jmz8r, Cluster md-rollout-t3zvld/md-rollout-pf4k1h: dialing host IP address at : dial tcp :22: connect: connection refused Failed to get logs for Machine md-rollout-pf4k1h-ww57s, Cluster md-rollout-t3zvld/md-rollout-pf4k1h: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 [1mSTEP:[0m Dumping all the Cluster API resources in the "md-rollout-t3zvld" namespace [38;5;243m@ 01/29/23 18:25:33.749[0m [1mSTEP:[0m Deleting cluster md-rollout-t3zvld/md-rollout-pf4k1h [38;5;243m@ 01/29/23 18:25:34.056[0m [1mSTEP:[0m Deleting cluster md-rollout-pf4k1h [38;5;243m@ 01/29/23 18:25:34.084[0m INFO: Waiting for the Cluster md-rollout-t3zvld/md-rollout-pf4k1h to be deleted [1mSTEP:[0m Waiting for cluster md-rollout-pf4k1h to be deleted [38;5;243m@ 01/29/23 18:25:34.099[0m [38;5;214m[TIMEDOUT][0m in [AfterEach] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/md_rollout.go:103 [38;5;243m@ 01/29/23 18:25:40.462[0m [38;5;9m• [FAILED] [1180.486 seconds][0m [0mClusterAPI Machine Deployment Tests [38;5;243mRunning the MachineDeployment rollout spec [38;5;9m[1m[It] Should successfully upgrade Machines upon changes in relevant MachineDeployment fields[0m [38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/md_rollout.go:71[0m [38;5;9m[FAILED] Timed out after 600.001s. Timed out waiting for 1 nodes to be created for MachineDeployment md-rollout-t3zvld/md-rollout-pf4k1h-md-0 Expected <int>: 0 to equal <int>: 1[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/29/23 18:25:31.551[0m ... skipping 12 lines ... [1mSTEP:[0m Cleaning up the vSphere session [38;5;243m@ 01/29/23 18:25:40.464[0m [1mSTEP:[0m Tearing down the management cluster [38;5;243m@ 01/29/23 18:25:40.587[0m [38;5;10m[SynchronizedAfterSuite] PASSED [1.670 seconds][0m [38;5;243m------------------------------[0m [38;5;9m[1mSummarizing 4 Failures:[0m [38;5;9m[FAIL][0m [0mLabel nodes with ESXi host info [38;5;9m[1m[It] creates a workload cluster whose nodes have the ESXi host info[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[FAIL][0m [0mCluster creation with storage policy [38;5;9m[1m[It] should create a cluster successfully[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[FAIL][0m [0mCluster Creation using Cluster API quick-start test [PR-Blocking] [38;5;9m[1m[It] Should create a workload cluster[0m [38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/controlplane_helpers.go:176[0m [38;5;9m[FAIL][0m [0mClusterAPI Machine Deployment Tests [38;5;243mRunning the MachineDeployment rollout spec [38;5;9m[1m[It] Should successfully upgrade Machines upon changes in relevant MachineDeployment fields[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 4 of 17 Specs in 3546.939 seconds[0m [38;5;9m[1mFAIL! - Suite Timeout Elapsed[0m -- [38;5;10m[1m0 Passed[0m | [38;5;9m[1m4 Failed[0m | [38;5;11m[1m1 Pending[0m | [38;5;14m[1m12 Skipped[0m --- FAIL: TestE2E (3546.94s) FAIL Ginkgo ran 1 suite in 1h0m1.771128448s Test Suite Failed real 60m1.791s user 5m39.831s sys 1m2.437s make: *** [Makefile:183: e2e] Error 1 Releasing IP claims ipclaim.ipam.metal3.io "ip-claim-0f20b9dab5022e274a53dd1cbcf6aca367784da9" deleted ipclaim.ipam.metal3.io "workload-ip-claim-29e5b1476d1a4a17d86ec29dd24b9981733f5c57" 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 ...