periodic-cluster-api-provider-vsphere-e2e-main #1616847324007370752
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 1h5m |
| Revision | main |
... skipping 591 lines ... INFO: Waiting for control plane to be ready INFO: Waiting for control plane quick-start-1rllr4/quick-start-7cpe5i 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/21/23 17:28:28.353[0m [1mSTEP:[0m Checking all the control plane machines are in the expected failure domains [38;5;243m@ 01/21/23 17:28:48.373[0m INFO: Waiting for the machine deployments to be provisioned [1mSTEP:[0m Waiting for the workload nodes to exist [38;5;243m@ 01/21/23 17:28:48.399[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/21/23 17:38:48.4[0m [1mSTEP:[0m Dumping logs from the "quick-start-7cpe5i" workload cluster [38;5;243m@ 01/21/23 17:38:48.4[0m Failed to get logs for Machine quick-start-7cpe5i-md-0-7444c8c5c4-bvszw, Cluster quick-start-1rllr4/quick-start-7cpe5i: dialing host IP address at 192.168.6.151: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain Failed to get logs for Machine quick-start-7cpe5i-ptt59, Cluster quick-start-1rllr4/quick-start-7cpe5i: dialing host IP address at 192.168.6.42: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain [1mSTEP:[0m Dumping all the Cluster API resources in the "quick-start-1rllr4" namespace [38;5;243m@ 01/21/23 17:38:51.037[0m [1mSTEP:[0m Deleting cluster quick-start-1rllr4/quick-start-7cpe5i [38;5;243m@ 01/21/23 17:38:51.321[0m [1mSTEP:[0m Deleting cluster quick-start-7cpe5i [38;5;243m@ 01/21/23 17:38:51.338[0m INFO: Waiting for the Cluster quick-start-1rllr4/quick-start-7cpe5i to be deleted [1mSTEP:[0m Waiting for cluster quick-start-7cpe5i to be deleted [38;5;243m@ 01/21/23 17:38:51.351[0m [1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 01/21/23 17:39:21.374[0m INFO: Deleting namespace quick-start-1rllr4 [38;5;9m• [FAILED] [915.694 seconds][0m [0mCluster creation with [Ignition] bootstrap [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.000s. Timed out waiting for 1 nodes to be created for MachineDeployment quick-start-1rllr4/quick-start-7cpe5i-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/21/23 17:38:48.4[0m ... skipping 55 lines ... INFO: Waiting for MachineDeployment rollout for MachineDeploymentTopology "md-0" (class "quick-start-worker") to complete. [1mSTEP:[0m Deleting a MachineDeploymentTopology in the Cluster Topology and wait for associated MachineDeployment to be deleted [38;5;243m@ 01/21/23 17:46:03.261[0m INFO: Removing MachineDeploymentTopology from the Cluster Topology. INFO: Waiting for MachineDeployment to be deleted. [1mSTEP:[0m PASSED! [38;5;243m@ 01/21/23 17:46:13.337[0m [1mSTEP:[0m Dumping logs from the "clusterclass-changes-n5im5k" workload cluster [38;5;243m@ 01/21/23 17:46:13.337[0m Failed to get logs for Machine clusterclass-changes-n5im5k-jhh5k-87dbj, Cluster clusterclass-changes-7zsw4b/clusterclass-changes-n5im5k: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 [1mSTEP:[0m Dumping all the Cluster API resources in the "clusterclass-changes-7zsw4b" namespace [38;5;243m@ 01/21/23 17:46:15.389[0m [1mSTEP:[0m Deleting cluster clusterclass-changes-7zsw4b/clusterclass-changes-n5im5k [38;5;243m@ 01/21/23 17:46:15.679[0m [1mSTEP:[0m Deleting cluster clusterclass-changes-n5im5k [38;5;243m@ 01/21/23 17:46:15.698[0m INFO: Waiting for the Cluster clusterclass-changes-7zsw4b/clusterclass-changes-n5im5k to be deleted [1mSTEP:[0m Waiting for cluster clusterclass-changes-n5im5k to be deleted [38;5;243m@ 01/21/23 17:46:15.709[0m [1mSTEP:[0m Deleting namespace used for hosting the "clusterclass-changes" test spec [38;5;243m@ 01/21/23 17:46:55.738[0m ... skipping 34 lines ... INFO: Waiting for the cluster infrastructure to be provisioned [1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/21/23 17:46:56.805[0m INFO: Waiting for control plane to be initialized INFO: Waiting for the first control plane machine managed by node-drain-l76xgo/node-drain-r8sirc to be provisioned [1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/21/23 17:47:16.847[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/21/23 17:57:16.848[0m [1mSTEP:[0m Dumping logs from the "node-drain-r8sirc" workload cluster [38;5;243m@ 01/21/23 17:57:16.848[0m Failed to get logs for Machine node-drain-r8sirc-glwpv, Cluster node-drain-l76xgo/node-drain-r8sirc: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine node-drain-r8sirc-md-0-745cbc678b-nwgsx, Cluster node-drain-l76xgo/node-drain-r8sirc: dialing host IP address at : dial tcp :22: connect: connection refused [1mSTEP:[0m Dumping all the Cluster API resources in the "node-drain-l76xgo" namespace [38;5;243m@ 01/21/23 17:57:19.009[0m [1mSTEP:[0m Deleting cluster node-drain-l76xgo/node-drain-r8sirc [38;5;243m@ 01/21/23 17:57:19.297[0m [1mSTEP:[0m Deleting cluster node-drain-r8sirc [38;5;243m@ 01/21/23 17:57:19.314[0m INFO: Waiting for the Cluster node-drain-l76xgo/node-drain-r8sirc to be deleted [1mSTEP:[0m Waiting for cluster node-drain-r8sirc to be deleted [38;5;243m@ 01/21/23 17:57:19.327[0m [1mSTEP:[0m Deleting namespace used for hosting the "node-drain" test spec [38;5;243m@ 01/21/23 17:57:39.34[0m INFO: Deleting namespace node-drain-l76xgo [38;5;9m• [FAILED] [643.600 seconds][0m [0mWhen testing node drain timeout [38;5;9m[1m[It] A node should be forcefully removed if it cannot be drained in time[0m [38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/node_drain_timeout.go:83[0m [38;5;9m[FAILED] Timed out after 600.001s. 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/21/23 17:57:16.848[0m [38;5;243m------------------------------[0m ... skipping 161 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@ 01/21/23 18:14:29.072[0m [1mSTEP:[0m Dumping logs from the "md-rollout-2r3ixm" workload cluster [38;5;243m@ 01/21/23 18:14:29.072[0m Failed to get logs for Machine md-rollout-2r3ixm-jmfmt, Cluster md-rollout-sljk2m/md-rollout-2r3ixm: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine md-rollout-2r3ixm-md-0-7ff4547bcf-6xsr5, Cluster md-rollout-sljk2m/md-rollout-2r3ixm: 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-sljk2m" namespace [38;5;243m@ 01/21/23 18:14:33.561[0m [1mSTEP:[0m Deleting cluster md-rollout-sljk2m/md-rollout-2r3ixm [38;5;243m@ 01/21/23 18:14:33.852[0m [1mSTEP:[0m Deleting cluster md-rollout-2r3ixm [38;5;243m@ 01/21/23 18:14:33.872[0m INFO: Waiting for the Cluster md-rollout-sljk2m/md-rollout-2r3ixm to be deleted [1mSTEP:[0m Waiting for cluster md-rollout-2r3ixm to be deleted [38;5;243m@ 01/21/23 18:14:33.884[0m [1mSTEP:[0m Deleting namespace used for hosting the "md-rollout" test spec [38;5;243m@ 01/21/23 18:15:03.901[0m ... skipping 47 lines ... INFO: Waiting for the machine pools to be provisioned [1mSTEP:[0m Scaling the MachineDeployment out to 3 [38;5;243m@ 01/21/23 18:20:05.36[0m INFO: Scaling machine deployment md-scale-oojooe/md-scale-4ar2h1-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@ 01/21/23 18:21:14.272[0m [1mSTEP:[0m Dumping logs from the "md-scale-4ar2h1" workload cluster [38;5;243m@ 01/21/23 18:21:14.274[0m Failed to get logs for Machine md-scale-4ar2h1-crst9, Cluster md-scale-oojooe/md-scale-4ar2h1: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine md-scale-4ar2h1-md-0-568c75fbdf-4hb4n, Cluster md-scale-oojooe/md-scale-4ar2h1: dialing host IP address at : dial tcp :22: connect: connection refused Failed to get logs for Machine md-scale-4ar2h1-md-0-568c75fbdf-h6rm7, Cluster md-scale-oojooe/md-scale-4ar2h1: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine md-scale-4ar2h1-md-0-568c75fbdf-hv6zd, Cluster md-scale-oojooe/md-scale-4ar2h1: dialing host IP address at : dial tcp :22: connect: connection refused [1mSTEP:[0m Dumping all the Cluster API resources in the "md-scale-oojooe" namespace [38;5;243m@ 01/21/23 18:21:19.044[0m [1mSTEP:[0m Deleting cluster md-scale-oojooe/md-scale-4ar2h1 [38;5;243m@ 01/21/23 18:21:19.389[0m [1mSTEP:[0m Deleting cluster md-scale-4ar2h1 [38;5;243m@ 01/21/23 18:21:19.411[0m INFO: Waiting for the Cluster md-scale-oojooe/md-scale-4ar2h1 to be deleted [1mSTEP:[0m Waiting for cluster md-scale-4ar2h1 to be deleted [38;5;243m@ 01/21/23 18:21:19.429[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@ 01/21/23 18:21:44.275[0m ... skipping 48 lines ... [1mSTEP:[0m Cleaning up the vSphere session [38;5;243m@ 01/21/23 18:21:44.277[0m [1mSTEP:[0m Tearing down the management cluster [38;5;243m@ 01/21/23 18:21:44.45[0m [38;5;10m[SynchronizedAfterSuite] PASSED [1.537 seconds][0m [38;5;243m------------------------------[0m [38;5;9m[1mSummarizing 3 Failures:[0m [38;5;9m[FAIL][0m [0mCluster creation with [Ignition] bootstrap [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/machinedeployment_helpers.go:131[0m [38;5;9m[FAIL][0m [0mWhen testing node drain timeout [38;5;9m[1m[It] A node should be forcefully removed if it cannot be drained in time[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 7 of 17 Specs in 3577.150 seconds[0m [38;5;9m[1mFAIL! - Suite Timeout Elapsed[0m -- [38;5;10m[1m4 Passed[0m | [38;5;9m[1m3 Failed[0m | [38;5;11m[1m1 Pending[0m | [38;5;14m[1m9 Skipped[0m --- FAIL: TestE2E (3577.15s) FAIL Ginkgo ran 1 suite in 1h0m31.632080783s Test Suite Failed real 60m31.653s user 5m37.929s sys 1m4.826s make: *** [Makefile:183: e2e] Error 1 Releasing IP claims ipclaim.ipam.metal3.io "ip-claim-6704eb0f771e33fed031fe371f17aea5def91b1e" deleted ipclaim.ipam.metal3.io "workload-ip-claim-7049f8ede8a7d6af77f599c55f88af35f3f2a426" 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 ...