periodic-cluster-api-provider-vsphere-e2e-main #1614672662708097024
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 1h5m |
| Revision | main |
... skipping 650 lines ... INFO: Waiting for correct number of replicas to exist [1mSTEP:[0m Scaling the MachineDeployment down to 1 [38;5;243m@ 01/15/23 17:35:27.284[0m INFO: Scaling machine deployment md-scale-87m0oi/md-scale-l1cdi7-md-0 from 3 to 1 replicas INFO: Waiting for correct number of replicas to exist [1mSTEP:[0m PASSED! [38;5;243m@ 01/15/23 17:35:37.392[0m [1mSTEP:[0m Dumping logs from the "md-scale-l1cdi7" workload cluster [38;5;243m@ 01/15/23 17:35:37.392[0m Failed to get logs for Machine md-scale-l1cdi7-j4gjm, Cluster md-scale-87m0oi/md-scale-l1cdi7: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine md-scale-l1cdi7-md-0-8545d75b77-t5s7m, Cluster md-scale-87m0oi/md-scale-l1cdi7: 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-87m0oi" namespace [38;5;243m@ 01/15/23 17:35:41.849[0m [1mSTEP:[0m Deleting cluster md-scale-87m0oi/md-scale-l1cdi7 [38;5;243m@ 01/15/23 17:35:42.144[0m [1mSTEP:[0m Deleting cluster md-scale-l1cdi7 [38;5;243m@ 01/15/23 17:35:42.16[0m INFO: Waiting for the Cluster md-scale-87m0oi/md-scale-l1cdi7 to be deleted [1mSTEP:[0m Waiting for cluster md-scale-l1cdi7 to be deleted [38;5;243m@ 01/15/23 17:35:42.175[0m [1mSTEP:[0m Deleting namespace used for hosting the "md-scale" test spec [38;5;243m@ 01/15/23 17:36:12.193[0m ... skipping 167 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/15/23 17:50:17.995[0m [1mSTEP:[0m Dumping logs from the "mhc-remediation-w77shv" workload cluster [38;5;243m@ 01/15/23 17:50:17.995[0m Failed to get logs for Machine mhc-remediation-w77shv-7tjrb, Cluster mhc-remediation-b0yuim/mhc-remediation-w77shv: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-w77shv-md-0-64d8f85758-psf2s, Cluster mhc-remediation-b0yuim/mhc-remediation-w77shv: 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-b0yuim" namespace [38;5;243m@ 01/15/23 17:50:22.107[0m [1mSTEP:[0m Deleting cluster mhc-remediation-b0yuim/mhc-remediation-w77shv [38;5;243m@ 01/15/23 17:50:22.422[0m [1mSTEP:[0m Deleting cluster mhc-remediation-w77shv [38;5;243m@ 01/15/23 17:50:22.441[0m INFO: Waiting for the Cluster mhc-remediation-b0yuim/mhc-remediation-w77shv to be deleted [1mSTEP:[0m Waiting for cluster mhc-remediation-w77shv to be deleted [38;5;243m@ 01/15/23 17:50:22.456[0m [1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 01/15/23 17:50:52.476[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/15/23 17:59:41.549[0m [1mSTEP:[0m Dumping logs from the "mhc-remediation-1qeo31" workload cluster [38;5;243m@ 01/15/23 17:59:41.549[0m Failed to get logs for Machine mhc-remediation-1qeo31-9hg86, Cluster mhc-remediation-jmvbyt/mhc-remediation-1qeo31: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-1qeo31-md-0-dfcb59879-lfrng, Cluster mhc-remediation-jmvbyt/mhc-remediation-1qeo31: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-1qeo31-p58zv, Cluster mhc-remediation-jmvbyt/mhc-remediation-1qeo31: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-1qeo31-w4jv2, Cluster mhc-remediation-jmvbyt/mhc-remediation-1qeo31: 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-jmvbyt" namespace [38;5;243m@ 01/15/23 17:59:48.904[0m [1mSTEP:[0m Deleting cluster mhc-remediation-jmvbyt/mhc-remediation-1qeo31 [38;5;243m@ 01/15/23 17:59:49.256[0m [1mSTEP:[0m Deleting cluster mhc-remediation-1qeo31 [38;5;243m@ 01/15/23 17:59:49.279[0m INFO: Waiting for the Cluster mhc-remediation-jmvbyt/mhc-remediation-1qeo31 to be deleted [1mSTEP:[0m Waiting for cluster mhc-remediation-1qeo31 to be deleted [38;5;243m@ 01/15/23 17:59:49.292[0m [1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 01/15/23 18:00:29.317[0m ... skipping 48 lines ... INFO: Waiting for the machine deployments to be provisioned [1mSTEP:[0m Waiting for the workload nodes to exist [38;5;243m@ 01/15/23 18:03:10.746[0m [1mSTEP:[0m Checking all the machines controlled by quick-start-7d9p7f-md-0 are in the "<None>" failure domain [38;5;243m@ 01/15/23 18:03:50.809[0m INFO: Waiting for the machine pools to be provisioned [1mSTEP:[0m PASSED! [38;5;243m@ 01/15/23 18:03:50.854[0m [1mSTEP:[0m Dumping logs from the "quick-start-7d9p7f" workload cluster [38;5;243m@ 01/15/23 18:03:50.854[0m Failed to get logs for Machine quick-start-7d9p7f-md-0-65cf5ddf9d-65rk7, Cluster quick-start-4ll0pc/quick-start-7d9p7f: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine quick-start-7d9p7f-mr92m, Cluster quick-start-4ll0pc/quick-start-7d9p7f: 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-4ll0pc" namespace [38;5;243m@ 01/15/23 18:03:55.229[0m [1mSTEP:[0m Deleting cluster quick-start-4ll0pc/quick-start-7d9p7f [38;5;243m@ 01/15/23 18:03:55.541[0m [1mSTEP:[0m Deleting cluster quick-start-7d9p7f [38;5;243m@ 01/15/23 18:03:55.566[0m INFO: Waiting for the Cluster quick-start-4ll0pc/quick-start-7d9p7f to be deleted [1mSTEP:[0m Waiting for cluster quick-start-7d9p7f to be deleted [38;5;243m@ 01/15/23 18:03:55.579[0m [1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 01/15/23 18:04:25.599[0m ... skipping 54 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/15/23 18:09:47.103[0m [1mSTEP:[0m Dumping logs from the "md-rollout-wrvaho" workload cluster [38;5;243m@ 01/15/23 18:09:47.103[0m Failed to get logs for Machine md-rollout-wrvaho-md-0-d54c8fcdd-z48vh, Cluster md-rollout-kjdhbq/md-rollout-wrvaho: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine md-rollout-wrvaho-p29nh, Cluster md-rollout-kjdhbq/md-rollout-wrvaho: 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-kjdhbq" namespace [38;5;243m@ 01/15/23 18:09:51.381[0m [1mSTEP:[0m Deleting cluster md-rollout-kjdhbq/md-rollout-wrvaho [38;5;243m@ 01/15/23 18:09:51.823[0m [1mSTEP:[0m Deleting cluster md-rollout-wrvaho [38;5;243m@ 01/15/23 18:09:51.843[0m INFO: Waiting for the Cluster md-rollout-kjdhbq/md-rollout-wrvaho to be deleted [1mSTEP:[0m Waiting for cluster md-rollout-wrvaho to be deleted [38;5;243m@ 01/15/23 18:09:51.868[0m [1mSTEP:[0m Deleting namespace used for hosting the "md-rollout" test spec [38;5;243m@ 01/15/23 18:10:21.892[0m ... skipping 129 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 32302 [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 32322 [sync.Cond.Wait][0m ... skipping 18 lines ... [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc000ba66c0, 0x3e}, {0xc000ba6700, 0x39}, {0xc0019f6de0, 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 6 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 32329 [sync.Cond.Wait][0m ... skipping 18 lines ... [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc0000570b0, 0x27}, {0xc000057140, 0x22}, {0xc001d8ed90, 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 29 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 32335 [sync.Cond.Wait][0m ... skipping 18 lines ... [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc00279b7a0, 0x28}, {0xc00279b7d0, 0x23}, {0xc0018cab94, 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}}, {{0xc000a6f980, 0x3a}, {0xc000a6fa00, 0x35}, {0xc00096aa40, 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 35 lines ... [38;5;9m[1mSummarizing 1 Failure:[0m [38;5;214m[TIMEDOUT][0m [0mCluster creation with storage policy [38;5;214m[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[1mRan 9 of 17 Specs in 3573.532 seconds[0m [38;5;9m[1mFAIL! - Suite Timeout Elapsed[0m -- [38;5;10m[1m8 Passed[0m | [38;5;9m[1m1 Failed[0m | [38;5;11m[1m1 Pending[0m | [38;5;14m[1m7 Skipped[0m --- FAIL: TestE2E (3573.53s) FAIL Ginkgo ran 1 suite in 1h0m31.787098038s Test Suite Failed real 60m31.812s user 6m11.703s sys 1m12.347s make: *** [Makefile:183: e2e] Error 1 Releasing IP claims ipclaim.ipam.metal3.io "ip-claim-fffe83f36f304a6484e0c502736cd3218f147759" deleted ipclaim.ipam.metal3.io "workload-ip-claim-7939e62f634bc49f12cfefac888d6f61eeb676ba" 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 ...