periodic-cluster-api-provider-vsphere-e2e-main #1618116645572579328
Recent runs || View in Spyglass
| Result | FAILURE |
| Tests | 0 failed / 0 succeeded |
| Started | |
| Elapsed | 1h5m |
| Revision | main |
... skipping 164 lines ... #18 exporting to image #18 exporting layers #18 exporting layers 0.5s done #18 writing image sha256:60d52355984e333031a768acd8eee3d11e9b0351caaa65521d3dd7fa0928cd71 done #18 naming to gcr.io/k8s-staging-cluster-api/capv-manager:e2e done #18 DONE 0.5s 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:60d52355984e333031a768acd8eee3d11e9b0351caaa65521d3dd7fa0928cd71 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 313 lines ... INFO: Waiting for correct number of replicas to exist [1mSTEP:[0m Scaling the MachineDeployment down to 1 [38;5;243m@ 01/25/23 05:40:03.46[0m INFO: Scaling machine deployment md-scale-dmryyv/md-scale-0zc4dw-md-0 from 3 to 1 replicas INFO: Waiting for correct number of replicas to exist [1mSTEP:[0m PASSED! [38;5;243m@ 01/25/23 05:40:13.589[0m [1mSTEP:[0m Dumping logs from the "md-scale-0zc4dw" workload cluster [38;5;243m@ 01/25/23 05:40:13.59[0m Failed to get logs for Machine md-scale-0zc4dw-md-0-57b79654d5-shnsm, Cluster md-scale-dmryyv/md-scale-0zc4dw: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine md-scale-0zc4dw-pd5qn, Cluster md-scale-dmryyv/md-scale-0zc4dw: 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-dmryyv" namespace [38;5;243m@ 01/25/23 05:40:18.206[0m [1mSTEP:[0m Deleting cluster md-scale-dmryyv/md-scale-0zc4dw [38;5;243m@ 01/25/23 05:40:18.575[0m [1mSTEP:[0m Deleting cluster md-scale-0zc4dw [38;5;243m@ 01/25/23 05:40:18.594[0m INFO: Waiting for the Cluster md-scale-dmryyv/md-scale-0zc4dw to be deleted [1mSTEP:[0m Waiting for cluster md-scale-0zc4dw to be deleted [38;5;243m@ 01/25/23 05:40:18.609[0m [1mSTEP:[0m Deleting namespace used for hosting the "md-scale" test spec [38;5;243m@ 01/25/23 05:40:48.632[0m ... skipping 167 lines ... INFO: Waiting for the machine deployments to be provisioned [1mSTEP:[0m Waiting for the workload nodes to exist [38;5;243m@ 01/25/23 05:57:34.342[0m [1mSTEP:[0m Checking all the machines controlled by quick-start-b1tiz5-md-0 are in the "<None>" failure domain [38;5;243m@ 01/25/23 05:58:44.447[0m INFO: Waiting for the machine pools to be provisioned [1mSTEP:[0m PASSED! [38;5;243m@ 01/25/23 05:58:44.489[0m [1mSTEP:[0m Dumping logs from the "quick-start-b1tiz5" workload cluster [38;5;243m@ 01/25/23 05:58:44.49[0m Failed to get logs for Machine quick-start-b1tiz5-cb7hc, Cluster quick-start-6eow41/quick-start-b1tiz5: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine quick-start-b1tiz5-md-0-7b4986d774-nxpnm, Cluster quick-start-6eow41/quick-start-b1tiz5: 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-6eow41" namespace [38;5;243m@ 01/25/23 05:58:48.966[0m [1mSTEP:[0m Deleting cluster quick-start-6eow41/quick-start-b1tiz5 [38;5;243m@ 01/25/23 05:58:49.291[0m [1mSTEP:[0m Deleting cluster quick-start-b1tiz5 [38;5;243m@ 01/25/23 05:58:49.308[0m INFO: Waiting for the Cluster quick-start-6eow41/quick-start-b1tiz5 to be deleted [1mSTEP:[0m Waiting for cluster quick-start-b1tiz5 to be deleted [38;5;243m@ 01/25/23 05:58:49.324[0m [1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 01/25/23 05:59:19.346[0m ... skipping 50 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/25/23 06:06:21.059[0m [1mSTEP:[0m Dumping logs from the "md-rollout-41gtgz" workload cluster [38;5;243m@ 01/25/23 06:06:21.059[0m Failed to get logs for Machine md-rollout-41gtgz-28fqx, Cluster md-rollout-zwvh9d/md-rollout-41gtgz: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine md-rollout-41gtgz-md-0-66fdcb699b-kvkxl, Cluster md-rollout-zwvh9d/md-rollout-41gtgz: 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-zwvh9d" namespace [38;5;243m@ 01/25/23 06:06:25.741[0m [1mSTEP:[0m Deleting cluster md-rollout-zwvh9d/md-rollout-41gtgz [38;5;243m@ 01/25/23 06:06:26.058[0m [1mSTEP:[0m Deleting cluster md-rollout-41gtgz [38;5;243m@ 01/25/23 06:06:26.083[0m INFO: Waiting for the Cluster md-rollout-zwvh9d/md-rollout-41gtgz to be deleted [1mSTEP:[0m Waiting for cluster md-rollout-41gtgz to be deleted [38;5;243m@ 01/25/23 06:06:26.1[0m [1mSTEP:[0m Deleting namespace used for hosting the "md-rollout" test spec [38;5;243m@ 01/25/23 06:06:56.12[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/25/23 06:12:52.955[0m [1mSTEP:[0m Dumping logs from the "mhc-remediation-kbpik8" workload cluster [38;5;243m@ 01/25/23 06:12:52.955[0m Failed to get logs for Machine mhc-remediation-kbpik8-h8rls, Cluster mhc-remediation-c7lwsg/mhc-remediation-kbpik8: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-kbpik8-md-0-7fc9f48df7-7sv9h, Cluster mhc-remediation-c7lwsg/mhc-remediation-kbpik8: 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-c7lwsg" namespace [38;5;243m@ 01/25/23 06:12:57.393[0m [1mSTEP:[0m Deleting cluster mhc-remediation-c7lwsg/mhc-remediation-kbpik8 [38;5;243m@ 01/25/23 06:12:57.719[0m [1mSTEP:[0m Deleting cluster mhc-remediation-kbpik8 [38;5;243m@ 01/25/23 06:12:57.739[0m INFO: Waiting for the Cluster mhc-remediation-c7lwsg/mhc-remediation-kbpik8 to be deleted [1mSTEP:[0m Waiting for cluster mhc-remediation-kbpik8 to be deleted [38;5;243m@ 01/25/23 06:12:57.753[0m [1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 01/25/23 06:13:27.78[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/25/23 06:23:41.176[0m [1mSTEP:[0m Dumping logs from the "mhc-remediation-4n8xk9" workload cluster [38;5;243m@ 01/25/23 06:23:41.176[0m Failed to get logs for Machine mhc-remediation-4n8xk9-klspb, Cluster mhc-remediation-7878bs/mhc-remediation-4n8xk9: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-4n8xk9-md-0-66f6649547-fqpw5, Cluster mhc-remediation-7878bs/mhc-remediation-4n8xk9: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-4n8xk9-wtt79, Cluster mhc-remediation-7878bs/mhc-remediation-4n8xk9: running command "cat /var/log/cloud-init-output.log": Process exited with status 1 Failed to get logs for Machine mhc-remediation-4n8xk9-z6cvv, Cluster mhc-remediation-7878bs/mhc-remediation-4n8xk9: 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-7878bs" namespace [38;5;243m@ 01/25/23 06:23:49.013[0m [1mSTEP:[0m Deleting cluster mhc-remediation-7878bs/mhc-remediation-4n8xk9 [38;5;243m@ 01/25/23 06:23:49.371[0m [1mSTEP:[0m Deleting cluster mhc-remediation-4n8xk9 [38;5;243m@ 01/25/23 06:23:49.39[0m INFO: Waiting for the Cluster mhc-remediation-7878bs/mhc-remediation-4n8xk9 to be deleted [1mSTEP:[0m Waiting for cluster mhc-remediation-4n8xk9 to be deleted [38;5;243m@ 01/25/23 06:23:49.406[0m [1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 01/25/23 06:24:29.433[0m ... skipping 36 lines ... [1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/25/23 06:24:30.817[0m INFO: Waiting for control plane to be initialized INFO: Waiting for the first control plane machine managed by clusterclass-changes-jwkt9b/clusterclass-changes-sp1wyt-zlbqk to be provisioned [1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/25/23 06:24:50.877[0m [38;5;214m[TIMEDOUT][0m in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/clusterclass_changes.go:132 [38;5;243m@ 01/25/23 06:25:44.428[0m [1mSTEP:[0m Dumping logs from the "clusterclass-changes-sp1wyt" workload cluster [38;5;243m@ 01/25/23 06:25:44.43[0m Failed to get logs for Machine clusterclass-changes-sp1wyt-md-0-p275v-5446fb48bc-6pb29, Cluster clusterclass-changes-jwkt9b/clusterclass-changes-sp1wyt: dialing host IP address at : dial tcp :22: connect: connection refused Failed to get logs for Machine clusterclass-changes-sp1wyt-zlbqk-p5nsb, Cluster clusterclass-changes-jwkt9b/clusterclass-changes-sp1wyt: dialing host IP address at : dial tcp :22: connect: connection refused [1mSTEP:[0m Dumping all the Cluster API resources in the "clusterclass-changes-jwkt9b" namespace [38;5;243m@ 01/25/23 06:25:44.522[0m [1mSTEP:[0m Deleting cluster clusterclass-changes-jwkt9b/clusterclass-changes-sp1wyt [38;5;243m@ 01/25/23 06:25:44.86[0m [1mSTEP:[0m Deleting cluster clusterclass-changes-sp1wyt [38;5;243m@ 01/25/23 06:25:44.884[0m INFO: Waiting for the Cluster clusterclass-changes-jwkt9b/clusterclass-changes-sp1wyt to be deleted [1mSTEP:[0m Waiting for cluster clusterclass-changes-sp1wyt to be deleted [38;5;243m@ 01/25/23 06:25:44.897[0m [38;5;214m[TIMEDOUT][0m in [AfterEach] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/clusterclass_changes.go:190 [38;5;243m@ 01/25/23 06:26:14.431[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 80452 [chan receive, 1 minutes][0m ... skipping 41 lines ... [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc001e3b860, 0x28}, {0xc001e3b890, 0x23}, {0xc0020192d4, 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}}, {{0xc000a88240, 0x3e}, {0xc000a88280, 0x39}, {0xc00204ef00, 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 33077 [sync.Cond.Wait, 1 minutes][0m ... skipping 18 lines ... [38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc001c7c800, 0x3a}, {0xc001c7c840, 0x35}, {0xc0012792e0, 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}}, {{0xc0027a5350, 0x27}, {0xc0027a5380, 0x22}, {0xc00201a710, 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 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 33080 [select, 1 minutes][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 { There were [1m[38;5;9madditional failures[0m detected. To view them in detail run [1mginkgo -vv[0m ... skipping 14 lines ... [38;5;9m[1mSummarizing 1 Failure:[0m [38;5;214m[TIMEDOUT][0m [0mWhen testing ClusterClass changes [ClusterClass] [38;5;214m[1m[It] Should successfully rollout the managed topology upon changes to the ClusterClass[0m [38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/clusterclass_changes.go:132[0m [38;5;9m[1mRan 9 of 17 Specs in 3573.177 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.18s) FAIL Ginkgo ran 1 suite in 1h0m31.679564585s Test Suite Failed real 60m31.701s user 6m24.630s sys 1m12.991s make: *** [Makefile:183: e2e] Error 1 Releasing IP claims ipclaim.ipam.metal3.io "ip-claim-bfb1cb66b64dbf0a309982db57ca8341be39478a" deleted ipclaim.ipam.metal3.io "workload-ip-claim-46e1dd714f86cd68c407de57f9b96f17c2705c43" 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 ...