periodic-cluster-api-provider-vsphere-e2e-main #1615216365038211072
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 1h5m |
| Revision | main |
... skipping 565 lines ... INFO: Waiting for the machine deployments to be provisioned [1mSTEP:[0m Waiting for the workload nodes to exist [38;5;243m@ 01/17/23 05:26:01.843[0m [1mSTEP:[0m Checking all the machines controlled by quick-start-na070d-md-0 are in the "<None>" failure domain [38;5;243m@ 01/17/23 05:27:11.932[0m INFO: Waiting for the machine pools to be provisioned [1mSTEP:[0m PASSED! [38;5;243m@ 01/17/23 05:27:11.97[0m [1mSTEP:[0m Dumping logs from the "quick-start-na070d" workload cluster [38;5;243m@ 01/17/23 05:27:11.97[0m Failed to get logs for Machine quick-start-na070d-md-0-744587f8fc-5g2jd, Cluster quick-start-9cecab/quick-start-na070d: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine quick-start-na070d-tdfp7, Cluster quick-start-9cecab/quick-start-na070d: 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-9cecab" namespace [38;5;243m@ 01/17/23 05:27:16.147[0m [1mSTEP:[0m Deleting cluster quick-start-9cecab/quick-start-na070d [38;5;243m@ 01/17/23 05:27:16.441[0m [1mSTEP:[0m Deleting cluster quick-start-na070d [38;5;243m@ 01/17/23 05:27:16.462[0m INFO: Waiting for the Cluster quick-start-9cecab/quick-start-na070d to be deleted [1mSTEP:[0m Waiting for cluster quick-start-na070d to be deleted [38;5;243m@ 01/17/23 05:27:16.475[0m [1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 01/17/23 05:27:46.494[0m ... skipping 232 lines ... INFO: Waiting for correct number of replicas to exist [1mSTEP:[0m Scaling the MachineDeployment down to 1 [38;5;243m@ 01/17/23 05:49:26.906[0m INFO: Scaling machine deployment md-scale-doljx9/md-scale-vilmm8-md-0 from 3 to 1 replicas INFO: Waiting for correct number of replicas to exist [1mSTEP:[0m PASSED! [38;5;243m@ 01/17/23 05:49:37.036[0m [1mSTEP:[0m Dumping logs from the "md-scale-vilmm8" workload cluster [38;5;243m@ 01/17/23 05:49:37.036[0m Failed to get logs for Machine md-scale-vilmm8-k4f4k, Cluster md-scale-doljx9/md-scale-vilmm8: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine md-scale-vilmm8-md-0-79d45dd854-xzx26, Cluster md-scale-doljx9/md-scale-vilmm8: 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-scale-doljx9" namespace [38;5;243m@ 01/17/23 05:49:41.733[0m [1mSTEP:[0m Deleting cluster md-scale-doljx9/md-scale-vilmm8 [38;5;243m@ 01/17/23 05:49:42.036[0m [1mSTEP:[0m Deleting cluster md-scale-vilmm8 [38;5;243m@ 01/17/23 05:49:42.054[0m INFO: Waiting for the Cluster md-scale-doljx9/md-scale-vilmm8 to be deleted [1mSTEP:[0m Waiting for cluster md-scale-vilmm8 to be deleted [38;5;243m@ 01/17/23 05:49:42.069[0m [1mSTEP:[0m Deleting namespace used for hosting the "md-scale" test spec [38;5;243m@ 01/17/23 05:50:12.089[0m ... skipping 52 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@ 01/17/23 05:56:28.475[0m [1mSTEP:[0m Dumping logs from the "mhc-remediation-48qrhy" workload cluster [38;5;243m@ 01/17/23 05:56:28.475[0m Failed to get logs for Machine mhc-remediation-48qrhy-b62tq, Cluster mhc-remediation-t7qqu2/mhc-remediation-48qrhy: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-48qrhy-md-0-6d57bbcf4d-wjt2g, Cluster mhc-remediation-t7qqu2/mhc-remediation-48qrhy: 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-t7qqu2" namespace [38;5;243m@ 01/17/23 05:56:32.63[0m [1mSTEP:[0m Deleting cluster mhc-remediation-t7qqu2/mhc-remediation-48qrhy [38;5;243m@ 01/17/23 05:56:32.963[0m [1mSTEP:[0m Deleting cluster mhc-remediation-48qrhy [38;5;243m@ 01/17/23 05:56:32.993[0m INFO: Waiting for the Cluster mhc-remediation-t7qqu2/mhc-remediation-48qrhy to be deleted [1mSTEP:[0m Waiting for cluster mhc-remediation-48qrhy to be deleted [38;5;243m@ 01/17/23 05:56:33.013[0m [1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 01/17/23 05:57:03.045[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@ 01/17/23 06:07:48.212[0m [1mSTEP:[0m Dumping logs from the "mhc-remediation-esnw7g" workload cluster [38;5;243m@ 01/17/23 06:07:48.212[0m Failed to get logs for Machine mhc-remediation-esnw7g-4zfn7, Cluster mhc-remediation-x4gh7l/mhc-remediation-esnw7g: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-esnw7g-md-0-547464dd5b-qflmx, Cluster mhc-remediation-x4gh7l/mhc-remediation-esnw7g: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-esnw7g-qbdqx, Cluster mhc-remediation-x4gh7l/mhc-remediation-esnw7g: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-esnw7g-xp5mw, Cluster mhc-remediation-x4gh7l/mhc-remediation-esnw7g: 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-x4gh7l" namespace [38;5;243m@ 01/17/23 06:07:55.417[0m [1mSTEP:[0m Deleting cluster mhc-remediation-x4gh7l/mhc-remediation-esnw7g [38;5;243m@ 01/17/23 06:07:55.722[0m [1mSTEP:[0m Deleting cluster mhc-remediation-esnw7g [38;5;243m@ 01/17/23 06:07:55.741[0m INFO: Waiting for the Cluster mhc-remediation-x4gh7l/mhc-remediation-esnw7g to be deleted [1mSTEP:[0m Waiting for cluster mhc-remediation-esnw7g to be deleted [38;5;243m@ 01/17/23 06:07:55.754[0m [1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 01/17/23 06:08:35.783[0m ... skipping 57 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/17/23 06:13:07.604[0m INFO: Removing MachineDeploymentTopology from the Cluster Topology. INFO: Waiting for MachineDeployment to be deleted. [1mSTEP:[0m PASSED! [38;5;243m@ 01/17/23 06:13:17.687[0m [1mSTEP:[0m Dumping logs from the "clusterclass-changes-xwfbdz" workload cluster [38;5;243m@ 01/17/23 06:13:17.687[0m Failed to get logs for Machine clusterclass-changes-xwfbdz-t2qcf-mt94r, Cluster clusterclass-changes-6z0oz8/clusterclass-changes-xwfbdz: 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-6z0oz8" namespace [38;5;243m@ 01/17/23 06:13:19.824[0m [1mSTEP:[0m Deleting cluster clusterclass-changes-6z0oz8/clusterclass-changes-xwfbdz [38;5;243m@ 01/17/23 06:13:20.117[0m [1mSTEP:[0m Deleting cluster clusterclass-changes-xwfbdz [38;5;243m@ 01/17/23 06:13:20.14[0m INFO: Waiting for the Cluster clusterclass-changes-6z0oz8/clusterclass-changes-xwfbdz to be deleted [1mSTEP:[0m Waiting for cluster clusterclass-changes-xwfbdz to be deleted [38;5;243m@ 01/17/23 06:13:20.152[0m [1mSTEP:[0m Deleting namespace used for hosting the "clusterclass-changes" test spec [38;5;243m@ 01/17/23 06:13:40.17[0m ... skipping 93 lines ... [1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/17/23 06:18:25.657[0m INFO: Waiting for control plane to be initialized INFO: Waiting for the first control plane machine managed by quick-start-3xmk83/quick-start-upwt0n to be provisioned [1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/17/23 06:19:15.712[0m [38;5;214m[TIMEDOUT][0m in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/quick_start.go:78 [38;5;243m@ 01/17/23 06:20:15.878[0m [1mSTEP:[0m Dumping logs from the "quick-start-upwt0n" workload cluster [38;5;243m@ 01/17/23 06:20:15.884[0m Failed to get logs for Machine quick-start-upwt0n-4jzdr, Cluster quick-start-3xmk83/quick-start-upwt0n: dialing host IP address at : dial tcp :22: connect: connection refused Failed to get logs for Machine quick-start-upwt0n-md-0-8544687b97-j6dtv, Cluster quick-start-3xmk83/quick-start-upwt0n: dialing host IP address at : dial tcp :22: connect: connection refused [1mSTEP:[0m Dumping all the Cluster API resources in the "quick-start-3xmk83" namespace [38;5;243m@ 01/17/23 06:20:15.953[0m [1mSTEP:[0m Deleting cluster quick-start-3xmk83/quick-start-upwt0n [38;5;243m@ 01/17/23 06:20:16.247[0m [1mSTEP:[0m Deleting cluster quick-start-upwt0n [38;5;243m@ 01/17/23 06:20:16.263[0m INFO: Waiting for the Cluster quick-start-3xmk83/quick-start-upwt0n to be deleted [1mSTEP:[0m Waiting for cluster quick-start-upwt0n to be deleted [38;5;243m@ 01/17/23 06:20:16.272[0m [38;5;214m[TIMEDOUT][0m in [AfterEach] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/quick_start.go:109 [38;5;243m@ 01/17/23 06:20:45.884[0m ... skipping 68 lines ... | for { [1m[38;5;214m> select {[0m | case <-ctx.Done(): | return [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225[0m | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment)) | [1m[38;5;214m> go func() {[0m | defer GinkgoRecover() | for { [38;5;214mgoroutine 81022 [chan receive, 2 minutes][0m ... skipping 26 lines ... | for { [1m[38;5;214m> select {[0m | case <-ctx.Done(): | return [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225[0m | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment)) | [1m[38;5;214m> go func() {[0m | defer GinkgoRecover() | for { [38;5;214mgoroutine 33363 [select][0m ... skipping 3 lines ... | for { [1m[38;5;214m> select {[0m | case <-ctx.Done(): | return [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225[0m | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment)) | [1m[38;5;214m> go func() {[0m | defer GinkgoRecover() | for { [38;5;214mgoroutine 33355 [select][0m ... skipping 3 lines ... | for { [1m[38;5;214m> select {[0m | case <-ctx.Done(): | return [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225[0m | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment)) | [1m[38;5;214m> go func() {[0m | defer GinkgoRecover() | for { [38;5;214mgoroutine 33347 [sync.Cond.Wait][0m ... skipping 18 lines ... [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc00200d9c0, 0x3a}, {0xc00200da40, 0x35}, {0xc001100840, 0x1d}, ...}, ...}, ...)[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186[0m | out := bufio.NewWriter(f) | defer out.Flush() [1m[38;5;214m> _, err = out.ReadFrom(podLogs)[0m | if err != nil && err != io.ErrUnexpectedEOF { | // Failing to stream logs should not cause the test to fail [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161[0m | | // Watch each container's logs in a goroutine so we can stream them all concurrently. [1m[38;5;214m> go func(pod corev1.Pod, container corev1.Container) {[0m | defer GinkgoRecover() ... skipping 21 lines ... [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc001fbec00, 0x27}, {0xc001fbec30, 0x22}, {0xc001892ae0, 0xb}, ...}, ...}, ...)[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186[0m | out := bufio.NewWriter(f) | defer out.Flush() [1m[38;5;214m> _, err = out.ReadFrom(podLogs)[0m | if err != nil && err != io.ErrUnexpectedEOF { | // Failing to stream logs should not cause the test to fail [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161[0m | | // Watch each container's logs in a goroutine so we can stream them all concurrently. [1m[38;5;214m> go func(pod corev1.Pod, container corev1.Container) {[0m | defer GinkgoRecover() ... skipping 21 lines ... [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc0010360c0, 0x3e}, {0xc001036100, 0x39}, {0xc002514450, 0x21}, ...}, ...}, ...)[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186[0m | out := bufio.NewWriter(f) | defer out.Flush() [1m[38;5;214m> _, err = out.ReadFrom(podLogs)[0m | if err != nil && err != io.ErrUnexpectedEOF { | // Failing to stream logs should not cause the test to fail [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161[0m | | // Watch each container's logs in a goroutine so we can stream them all concurrently. [1m[38;5;214m> go func(pod corev1.Pod, container corev1.Container) {[0m | defer GinkgoRecover() ... skipping 21 lines ... [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc0022350b0, 0x28}, {0xc0022350e0, 0x23}, {0xc002219ca4, 0xb}, ...}, ...}, ...)[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186[0m | out := bufio.NewWriter(f) | defer out.Flush() [1m[38;5;214m> _, err = out.ReadFrom(podLogs)[0m | if err != nil && err != io.ErrUnexpectedEOF { | // Failing to stream logs should not cause the test to fail [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs[0m [38;5;214m[1m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161[0m | | // Watch each container's logs in a goroutine so we can stream them all concurrently. [1m[38;5;214m> go func(pod corev1.Pod, container corev1.Container) {[0m | defer GinkgoRecover() ... skipping 35 lines ... [38;5;9m[1mSummarizing 1 Failure:[0m [38;5;214m[TIMEDOUT][0m [0mCluster creation with [Ignition] bootstrap [PR-Blocking] [38;5;214m[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[1mRan 10 of 17 Specs in 3577.501 seconds[0m [38;5;9m[1mFAIL! - Suite Timeout Elapsed[0m -- [38;5;10m[1m9 Passed[0m | [38;5;9m[1m1 Failed[0m | [38;5;11m[1m1 Pending[0m | [38;5;14m[1m6 Skipped[0m --- FAIL: TestE2E (3577.50s) FAIL Ginkgo ran 1 suite in 1h0m31.840258334s Test Suite Failed real 60m31.863s user 5m47.670s sys 1m11.926s make: *** [Makefile:183: e2e] Error 1 Releasing IP claims ipclaim.ipam.metal3.io "ip-claim-0bddd611cc8aa46803abc3b09c5d65b813f73678" deleted ipclaim.ipam.metal3.io "workload-ip-claim-e28565e08de05b55f70f1ea7529ddcfea9799969" 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 ...