periodic-cluster-api-provider-vsphere-e2e-main #1621378761020674048
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 1h6m |
| Revision | main |
... skipping 164 lines ... #18 exporting to image #18 exporting layers #18 exporting layers 0.4s done #18 writing image sha256:b76fb2493ed9d3a899fbc9646e1f89e7c5cb46288bc0a3f9d9269d1b4e072c9c 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] - - [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:b76fb2493ed9d3a899fbc9646e1f89e7c5cb46288bc0a3f9d9269d1b4e072c9c 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@ 02/03/23 05:31:45.059[0m INFO: Waiting for control plane to be initialized INFO: Waiting for the first control plane machine managed by capv-e2e-j5luq4/storage-policy-f1jh5g to be provisioned [1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 02/03/23 05:32:15.102[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@ 02/03/23 05:42:15.106[0m [1mSTEP:[0m Dumping all the Cluster API resources in the "capv-e2e-j5luq4" namespace [38;5;243m@ 02/03/23 05:42:15.106[0m [1mSTEP:[0m cleaning up namespace: capv-e2e-j5luq4 [38;5;243m@ 02/03/23 05:42:15.572[0m [1mSTEP:[0m Deleting cluster storage-policy-f1jh5g [38;5;243m@ 02/03/23 05:42:15.599[0m INFO: Waiting for the Cluster capv-e2e-j5luq4/storage-policy-f1jh5g to be deleted [1mSTEP:[0m Waiting for cluster storage-policy-f1jh5g to be deleted [38;5;243m@ 02/03/23 05:42:15.621[0m [1mSTEP:[0m Deleting namespace used for hosting test spec [38;5;243m@ 02/03/23 05:42:35.64[0m INFO: Deleting namespace capv-e2e-j5luq4 [38;5;9m• [FAILED] [653.021 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.003s. 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@ 02/03/23 05:42:15.106[0m [38;5;243m------------------------------[0m ... skipping 41 lines ... INFO: Waiting for the machine deployments to be provisioned [1mSTEP:[0m Waiting for the workload nodes to exist [38;5;243m@ 02/03/23 05:45:08.875[0m [1mSTEP:[0m Checking all the machines controlled by quick-start-nrva3z-md-0-x6qc6 are in the "<None>" failure domain [38;5;243m@ 02/03/23 05:46:38.975[0m INFO: Waiting for the machine pools to be provisioned [1mSTEP:[0m PASSED! [38;5;243m@ 02/03/23 05:46:39.016[0m [1mSTEP:[0m Dumping logs from the "quick-start-nrva3z" workload cluster [38;5;243m@ 02/03/23 05:46:39.016[0m Failed to get logs for Machine quick-start-nrva3z-6hx72-n6cp6, Cluster quick-start-rzrgxy/quick-start-nrva3z: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine quick-start-nrva3z-md-0-x6qc6-655995595b-vgsnr, Cluster quick-start-rzrgxy/quick-start-nrva3z: 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-rzrgxy" namespace [38;5;243m@ 02/03/23 05:46:43.522[0m [1mSTEP:[0m Deleting cluster quick-start-rzrgxy/quick-start-nrva3z [38;5;243m@ 02/03/23 05:46:43.828[0m [1mSTEP:[0m Deleting cluster quick-start-nrva3z [38;5;243m@ 02/03/23 05:46:43.85[0m INFO: Waiting for the Cluster quick-start-rzrgxy/quick-start-nrva3z to be deleted [1mSTEP:[0m Waiting for cluster quick-start-nrva3z to be deleted [38;5;243m@ 02/03/23 05:46:43.861[0m [1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 02/03/23 05:47:23.887[0m ... skipping 44 lines ... INFO: Waiting for the machine deployments to be provisioned [1mSTEP:[0m Waiting for the workload nodes to exist [38;5;243m@ 02/03/23 05:49:45.195[0m [1mSTEP:[0m Checking all the machines controlled by quick-start-1jyiio-md-0 are in the "<None>" failure domain [38;5;243m@ 02/03/23 05:51:25.31[0m INFO: Waiting for the machine pools to be provisioned [1mSTEP:[0m PASSED! [38;5;243m@ 02/03/23 05:51:25.344[0m [1mSTEP:[0m Dumping logs from the "quick-start-1jyiio" workload cluster [38;5;243m@ 02/03/23 05:51:25.344[0m Failed to get logs for Machine quick-start-1jyiio-fztw8, Cluster quick-start-etjt1u/quick-start-1jyiio: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine quick-start-1jyiio-md-0-6795487b96-p7plk, Cluster quick-start-etjt1u/quick-start-1jyiio: 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-etjt1u" namespace [38;5;243m@ 02/03/23 05:51:29.997[0m [1mSTEP:[0m Deleting cluster quick-start-etjt1u/quick-start-1jyiio [38;5;243m@ 02/03/23 05:51:30.272[0m [1mSTEP:[0m Deleting cluster quick-start-1jyiio [38;5;243m@ 02/03/23 05:51:30.292[0m INFO: Waiting for the Cluster quick-start-etjt1u/quick-start-1jyiio to be deleted [1mSTEP:[0m Waiting for cluster quick-start-1jyiio to be deleted [38;5;243m@ 02/03/23 05:51:30.304[0m [1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 02/03/23 05:52:00.321[0m ... skipping 118 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 [1mSTEP:[0m PASSED! [38;5;243m@ 02/03/23 06:05:33.754[0m [1mSTEP:[0m Dumping logs from the "mhc-remediation-2z3sh7" workload cluster [38;5;243m@ 02/03/23 06:05:33.754[0m Failed to get logs for Machine mhc-remediation-2z3sh7-d8lqv, Cluster mhc-remediation-l9zy7q/mhc-remediation-2z3sh7: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-2z3sh7-md-0-6f6bb56c75-t4fx7, Cluster mhc-remediation-l9zy7q/mhc-remediation-2z3sh7: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 [1mSTEP:[0m Dumping all the Cluster API resources in the "mhc-remediation-l9zy7q" namespace [38;5;243m@ 02/03/23 06:05:37.836[0m [1mSTEP:[0m Deleting cluster mhc-remediation-l9zy7q/mhc-remediation-2z3sh7 [38;5;243m@ 02/03/23 06:05:38.144[0m [1mSTEP:[0m Deleting cluster mhc-remediation-2z3sh7 [38;5;243m@ 02/03/23 06:05:38.163[0m INFO: Waiting for the Cluster mhc-remediation-l9zy7q/mhc-remediation-2z3sh7 to be deleted [1mSTEP:[0m Waiting for cluster mhc-remediation-2z3sh7 to be deleted [38;5;243m@ 02/03/23 06:05:38.177[0m [1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 02/03/23 06:06:08.195[0m ... 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 [1mSTEP:[0m PASSED! [38;5;243m@ 02/03/23 06:15:11.943[0m [1mSTEP:[0m Dumping logs from the "mhc-remediation-ihai5w" workload cluster [38;5;243m@ 02/03/23 06:15:11.943[0m Failed to get logs for Machine mhc-remediation-ihai5w-8wfwb, Cluster mhc-remediation-7ymkv8/mhc-remediation-ihai5w: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-ihai5w-bs2hq, Cluster mhc-remediation-7ymkv8/mhc-remediation-ihai5w: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-ihai5w-jvw5x, Cluster mhc-remediation-7ymkv8/mhc-remediation-ihai5w: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-ihai5w-md-0-68bf55578b-8s96d, Cluster mhc-remediation-7ymkv8/mhc-remediation-ihai5w: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 [1mSTEP:[0m Dumping all the Cluster API resources in the "mhc-remediation-7ymkv8" namespace [38;5;243m@ 02/03/23 06:15:19.841[0m [1mSTEP:[0m Deleting cluster mhc-remediation-7ymkv8/mhc-remediation-ihai5w [38;5;243m@ 02/03/23 06:15:20.15[0m [1mSTEP:[0m Deleting cluster mhc-remediation-ihai5w [38;5;243m@ 02/03/23 06:15:20.17[0m INFO: Waiting for the Cluster mhc-remediation-7ymkv8/mhc-remediation-ihai5w to be deleted [1mSTEP:[0m Waiting for cluster mhc-remediation-ihai5w to be deleted [38;5;243m@ 02/03/23 06:15:20.183[0m [1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 02/03/23 06:16:00.208[0m ... skipping 52 lines ... INFO: Waiting for rolling upgrade to start. INFO: Waiting for MachineDeployment rolling upgrade to start INFO: Waiting for rolling upgrade to complete. INFO: Waiting for MachineDeployment rolling upgrade to complete [1mSTEP:[0m PASSED! [38;5;243m@ 02/03/23 06:22:01.839[0m [1mSTEP:[0m Dumping logs from the "md-rollout-znvvvc" workload cluster [38;5;243m@ 02/03/23 06:22:01.839[0m Failed to get logs for Machine md-rollout-znvvvc-md-0-69b7c77888-qbwnl, Cluster md-rollout-emiino/md-rollout-znvvvc: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine md-rollout-znvvvc-t2j4h, Cluster md-rollout-emiino/md-rollout-znvvvc: 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-emiino" namespace [38;5;243m@ 02/03/23 06:22:05.802[0m [1mSTEP:[0m Deleting cluster md-rollout-emiino/md-rollout-znvvvc [38;5;243m@ 02/03/23 06:22:06.075[0m [1mSTEP:[0m Deleting cluster md-rollout-znvvvc [38;5;243m@ 02/03/23 06:22:06.092[0m INFO: Waiting for the Cluster md-rollout-emiino/md-rollout-znvvvc to be deleted [1mSTEP:[0m Waiting for cluster md-rollout-znvvvc to be deleted [38;5;243m@ 02/03/23 06:22:06.105[0m [1mSTEP:[0m Deleting namespace used for hosting the "md-rollout" test spec [38;5;243m@ 02/03/23 06:22:36.122[0m ... skipping 49 lines ... INFO: Scaling machine deployment md-scale-78a88v/md-scale-dth0vm-md-0 from 1 to 3 replicas INFO: Waiting for correct number of replicas to exist [38;5;214m[TIMEDOUT][0m in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/md_scale.go:71 [38;5;243m@ 02/03/23 06:28:25.591[0m [1mSTEP:[0m Dumping logs from the "md-scale-dth0vm" workload cluster [38;5;243m@ 02/03/23 06:28:25.592[0m [1mSTEP:[0m Scaling the MachineDeployment down to 1 [38;5;243m@ 02/03/23 06:28:28.016[0m INFO: Scaling machine deployment md-scale-78a88v/md-scale-dth0vm-md-0 from 3 to 1 replicas Failed to get logs for Machine md-scale-dth0vm-fvn24, Cluster md-scale-78a88v/md-scale-dth0vm: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 INFO: Waiting for correct number of replicas to exist Failed to get logs for Machine md-scale-dth0vm-md-0-65cf46fc64-c5fzh, Cluster md-scale-78a88v/md-scale-dth0vm: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 [1mSTEP:[0m PASSED! [38;5;243m@ 02/03/23 06:28:38.146[0m [38;5;214m[TIMEDOUT][0m in [AfterEach] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/md_scale.go:115 [38;5;243m@ 02/03/23 06:28:55.592[0m [38;5;214m• [TIMEDOUT] [379.455 seconds][0m [0mWhen testing MachineDeployment scale out/in [38;5;214m[1m[It] Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count[0m [38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/md_scale.go:71[0m ... skipping 44 lines ... [1mSTEP:[0m Cleaning up the vSphere session [38;5;243m@ 02/03/23 06:28:55.594[0m [1mSTEP:[0m Tearing down the management cluster [38;5;243m@ 02/03/23 06:28:55.776[0m [38;5;10m[SynchronizedAfterSuite] PASSED [1.532 seconds][0m [38;5;243m------------------------------[0m [38;5;9m[1mSummarizing 2 Failures:[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;214m[TIMEDOUT][0m [0mWhen testing MachineDeployment scale out/in [38;5;214m[1m[It] Should successfully scale a MachineDeployment up and down upon changes to the MachineDeployment replica count[0m [38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/md_scale.go:71[0m [38;5;9m[1mRan 8 of 17 Specs in 3547.166 seconds[0m [38;5;9m[1mFAIL! - Suite Timeout Elapsed[0m -- [38;5;10m[1m6 Passed[0m | [38;5;9m[1m2 Failed[0m | [38;5;11m[1m1 Pending[0m | [38;5;14m[1m8 Skipped[0m --- FAIL: TestE2E (3547.17s) FAIL Ginkgo ran 1 suite in 1h0m31.626631418s Test Suite Failed real 60m31.674s user 7m43.142s sys 2m7.788s make: *** [Makefile:183: e2e] Error 1 Releasing IP claims ipclaim.ipam.metal3.io "ip-claim-a290dd722d4d65dbabc03827655bf855aa44aa31" deleted ipclaim.ipam.metal3.io "workload-ip-claim-140e3b2044277ff78d0e35d377a271a82bf13cfe" 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 ...