This job view page is being replaced by Spyglass soon.
Check out the new job view.
Error lines from build-log.txt
... skipping 645 lines ...
INFO: Waiting for correct number of replicas to exist
[1mSTEP:[0m Scaling the MachineDeployment down to 1 [38;5;243m@ 01/17/23 17:36:28.302[0m
INFO: Scaling machine deployment md-scale-g5rdf4/md-scale-0wzhw0-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 17:36:38.438[0m
[1mSTEP:[0m Dumping logs from the "md-scale-0wzhw0" workload cluster [38;5;243m@ 01/17/23 17:36:38.438[0m
Failed to get logs for Machine md-scale-0wzhw0-md-0-54cd5b457-tkt97, Cluster md-scale-g5rdf4/md-scale-0wzhw0: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine md-scale-0wzhw0-spmxb, Cluster md-scale-g5rdf4/md-scale-0wzhw0: 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-g5rdf4" namespace [38;5;243m@ 01/17/23 17:36:43.002[0m
[1mSTEP:[0m Deleting cluster md-scale-g5rdf4/md-scale-0wzhw0 [38;5;243m@ 01/17/23 17:36:43.333[0m
[1mSTEP:[0m Deleting cluster md-scale-0wzhw0 [38;5;243m@ 01/17/23 17:36:43.353[0m
INFO: Waiting for the Cluster md-scale-g5rdf4/md-scale-0wzhw0 to be deleted
[1mSTEP:[0m Waiting for cluster md-scale-0wzhw0 to be deleted [38;5;243m@ 01/17/23 17:36:43.369[0m
[1mSTEP:[0m Deleting namespace used for hosting the "md-scale" test spec [38;5;243m@ 01/17/23 17:37:13.391[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@ 01/17/23 17:39:34.982[0m
[1mSTEP:[0m Checking all the machines controlled by quick-start-xzuyoo-md-0 are in the "<None>" failure domain [38;5;243m@ 01/17/23 17:40:45.119[0m
INFO: Waiting for the machine pools to be provisioned
[1mSTEP:[0m PASSED! [38;5;243m@ 01/17/23 17:40:45.164[0m
[1mSTEP:[0m Dumping logs from the "quick-start-xzuyoo" workload cluster [38;5;243m@ 01/17/23 17:40:45.164[0m
Failed to get logs for Machine quick-start-xzuyoo-md-0-65f86bf76c-m6xf7, Cluster quick-start-tf6ntp/quick-start-xzuyoo: dialing host IP address at 192.168.6.133: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
Failed to get logs for Machine quick-start-xzuyoo-zf4xn, Cluster quick-start-tf6ntp/quick-start-xzuyoo: dialing host IP address at 192.168.6.31: 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-tf6ntp" namespace [38;5;243m@ 01/17/23 17:40:47.636[0m
[1mSTEP:[0m Deleting cluster quick-start-tf6ntp/quick-start-xzuyoo [38;5;243m@ 01/17/23 17:40:47.956[0m
[1mSTEP:[0m Deleting cluster quick-start-xzuyoo [38;5;243m@ 01/17/23 17:40:47.978[0m
INFO: Waiting for the Cluster quick-start-tf6ntp/quick-start-xzuyoo to be deleted
[1mSTEP:[0m Waiting for cluster quick-start-xzuyoo to be deleted [38;5;243m@ 01/17/23 17:40:47.994[0m
[1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 01/17/23 17:41:18.016[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@ 01/17/23 17:43:59.754[0m
[1mSTEP:[0m Checking all the machines controlled by quick-start-yakrou-md-0-pmrf6 are in the "<None>" failure domain [38;5;243m@ 01/17/23 17:45:19.866[0m
INFO: Waiting for the machine pools to be provisioned
[1mSTEP:[0m PASSED! [38;5;243m@ 01/17/23 17:45:19.905[0m
[1mSTEP:[0m Dumping logs from the "quick-start-yakrou" workload cluster [38;5;243m@ 01/17/23 17:45:19.905[0m
Failed to get logs for Machine quick-start-yakrou-58v8r-km6hq, Cluster quick-start-usxan2/quick-start-yakrou: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine quick-start-yakrou-md-0-pmrf6-65cdbc84b9-dbpxl, Cluster quick-start-usxan2/quick-start-yakrou: 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-usxan2" namespace [38;5;243m@ 01/17/23 17:45:24.41[0m
[1mSTEP:[0m Deleting cluster quick-start-usxan2/quick-start-yakrou [38;5;243m@ 01/17/23 17:45:24.746[0m
[1mSTEP:[0m Deleting cluster quick-start-yakrou [38;5;243m@ 01/17/23 17:45:24.768[0m
INFO: Waiting for the Cluster quick-start-usxan2/quick-start-yakrou to be deleted
[1mSTEP:[0m Waiting for cluster quick-start-yakrou to be deleted [38;5;243m@ 01/17/23 17:45:24.781[0m
[1mSTEP:[0m Deleting namespace used for hosting the "quick-start" test spec [38;5;243m@ 01/17/23 17:45:54.804[0m
... skipping 174 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/17/23 18:03:34.294[0m
[1mSTEP:[0m Dumping logs from the "md-rollout-8d7147" workload cluster [38;5;243m@ 01/17/23 18:03:34.294[0m
Failed to get logs for Machine md-rollout-8d7147-8xgt9, Cluster md-rollout-g7to6q/md-rollout-8d7147: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine md-rollout-8d7147-md-0-589cd4d85b-2ht69, Cluster md-rollout-g7to6q/md-rollout-8d7147: 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-g7to6q" namespace [38;5;243m@ 01/17/23 18:03:38.7[0m
[1mSTEP:[0m Deleting cluster md-rollout-g7to6q/md-rollout-8d7147 [38;5;243m@ 01/17/23 18:03:39.06[0m
[1mSTEP:[0m Deleting cluster md-rollout-8d7147 [38;5;243m@ 01/17/23 18:03:39.081[0m
INFO: Waiting for the Cluster md-rollout-g7to6q/md-rollout-8d7147 to be deleted
[1mSTEP:[0m Waiting for cluster md-rollout-8d7147 to be deleted [38;5;243m@ 01/17/23 18:03:39.094[0m
[1mSTEP:[0m Deleting namespace used for hosting the "md-rollout" test spec [38;5;243m@ 01/17/23 18:04:09.115[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 18:08:41.108[0m
INFO: Removing MachineDeploymentTopology from the Cluster Topology.
INFO: Waiting for MachineDeployment to be deleted.
[1mSTEP:[0m PASSED! [38;5;243m@ 01/17/23 18:08:51.193[0m
[1mSTEP:[0m Dumping logs from the "clusterclass-changes-10fzd8" workload cluster [38;5;243m@ 01/17/23 18:08:51.193[0m
Failed to get logs for Machine clusterclass-changes-10fzd8-z57vg-qr6gg, Cluster clusterclass-changes-l44ccr/clusterclass-changes-10fzd8: 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-l44ccr" namespace [38;5;243m@ 01/17/23 18:08:53.387[0m
[1mSTEP:[0m Deleting cluster clusterclass-changes-l44ccr/clusterclass-changes-10fzd8 [38;5;243m@ 01/17/23 18:08:53.718[0m
[1mSTEP:[0m Deleting cluster clusterclass-changes-10fzd8 [38;5;243m@ 01/17/23 18:08:53.747[0m
INFO: Waiting for the Cluster clusterclass-changes-l44ccr/clusterclass-changes-10fzd8 to be deleted
[1mSTEP:[0m Waiting for cluster clusterclass-changes-10fzd8 to be deleted [38;5;243m@ 01/17/23 18:08:53.76[0m
[1mSTEP:[0m Deleting namespace used for hosting the "clusterclass-changes" test spec [38;5;243m@ 01/17/23 18:09:13.776[0m
... skipping 110 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 18:19:48.618[0m
[1mSTEP:[0m Dumping logs from the "mhc-remediation-qo9buw" workload cluster [38;5;243m@ 01/17/23 18:19:48.618[0m
Failed to get logs for Machine mhc-remediation-qo9buw-md-0-6f7ccc77f9-ppdkq, Cluster mhc-remediation-c4xjx2/mhc-remediation-qo9buw: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine mhc-remediation-qo9buw-pwkn6, Cluster mhc-remediation-c4xjx2/mhc-remediation-qo9buw: 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-c4xjx2" namespace [38;5;243m@ 01/17/23 18:19:53.132[0m
[1mSTEP:[0m Deleting cluster mhc-remediation-c4xjx2/mhc-remediation-qo9buw [38;5;243m@ 01/17/23 18:19:53.452[0m
[1mSTEP:[0m Deleting cluster mhc-remediation-qo9buw [38;5;243m@ 01/17/23 18:19:53.469[0m
INFO: Waiting for the Cluster mhc-remediation-c4xjx2/mhc-remediation-qo9buw to be deleted
[1mSTEP:[0m Waiting for cluster mhc-remediation-qo9buw to be deleted [38;5;243m@ 01/17/23 18:19:53.486[0m
[1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 01/17/23 18:20:23.509[0m
... skipping 37 lines ...
[1mSTEP:[0m Waiting for cluster to enter the provisioned phase [38;5;243m@ 01/17/23 18:20:24.854[0m
INFO: Waiting for control plane to be initialized
INFO: Waiting for the first control plane machine managed by mhc-remediation-av6esl/mhc-remediation-710kz1 to be provisioned
[1mSTEP:[0m Waiting for one control plane node to exist [38;5;243m@ 01/17/23 18:21:04.907[0m
[38;5;214m[TIMEDOUT][0m in [It] - /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/mhc_remediations.go:116 [38;5;243m@ 01/17/23 18:21:23.477[0m
[1mSTEP:[0m Dumping logs from the "mhc-remediation-710kz1" workload cluster [38;5;243m@ 01/17/23 18:21:23.479[0m
Failed to get logs for Machine mhc-remediation-710kz1-6rnnb, Cluster mhc-remediation-av6esl/mhc-remediation-710kz1: dialing host IP address at : dial tcp :22: connect: connection refused
Failed to get logs for Machine mhc-remediation-710kz1-md-0-5f67c9665-4nkg5, Cluster mhc-remediation-av6esl/mhc-remediation-710kz1: dialing host IP address at : dial tcp :22: connect: connection refused
[1mSTEP:[0m Dumping all the Cluster API resources in the "mhc-remediation-av6esl" namespace [38;5;243m@ 01/17/23 18:21:23.545[0m
[1mSTEP:[0m Deleting cluster mhc-remediation-av6esl/mhc-remediation-710kz1 [38;5;243m@ 01/17/23 18:21:23.872[0m
[1mSTEP:[0m Deleting cluster mhc-remediation-710kz1 [38;5;243m@ 01/17/23 18:21:23.89[0m
INFO: Waiting for the Cluster mhc-remediation-av6esl/mhc-remediation-710kz1 to be deleted
[1mSTEP:[0m Waiting for cluster mhc-remediation-710kz1 to be deleted [38;5;243m@ 01/17/23 18:21:23.901[0m
[1mSTEP:[0m Deleting namespace used for hosting the "mhc-remediation" test spec [38;5;243m@ 01/17/23 18:21:43.914[0m
... skipping 84 lines ...
[38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc002694030, 0x28}, {0xc002694060, 0x23}, {0xc002a89cf4, 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 44092 [sync.Cond.Wait][0m
... skipping 18 lines ...
[38;5;214m[1m> sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc00173ae80, 0x3a}, {0xc00173aec0, 0x35}, {0xc000cdb9a0, 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}}, {{0xc00173ba40, 0x3e}, {0xc00173ba80, 0x39}, {0xc0023d2420, 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}}, {{0xc00215be30, 0x27}, {0xc00215be60, 0x22}, {0xc00235bf44, 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 44115 [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 44146 [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;243m------------------------------[0m
[38;5;14mS [SKIPPED][0m
... skipping 17 lines ...
[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;243m------------------------------[0m
[0m[1m[SynchronizedAfterSuite] [0m
[38;5;243m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-vsphere/test/e2e/e2e_suite_test.go:159[0m
[1mSTEP:[0m Cleaning up the vSphere session [38;5;243m@ 01/17/23 18:21:43.938[0m
[1mSTEP:[0m Tearing down the management cluster [38;5;243m@ 01/17/23 18:21:44.115[0m
INFO: Failed to list the machines: Get "https://127.0.0.1:36063/apis/cluster.x-k8s.io/v1beta1/namespaces/mhc-remediation-av6esl/machines?labelSelector=cluster.x-k8s.io%2Fcluster-name%3Dmhc-remediation-710kz1%2Ccluster.x-k8s.io%2Fcontrol-plane%3D": dial tcp 127.0.0.1:36063: connect: connection refused
[38;5;10m[SynchronizedAfterSuite] PASSED [1.825 seconds][0m
[38;5;243m------------------------------[0m
[38;5;9m[1mSummarizing 1 Failure:[0m
[38;5;214m[TIMEDOUT][0m [0mWhen testing unhealthy machines remediation [38;5;214m[1m[It] Should successfully trigger KCP remediation[0m
[38;5;243m/home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/mhc_remediations.go:116[0m
[38;5;9m[1mRan 11 of 17 Specs in 3559.719 seconds[0m
[38;5;9m[1mFAIL! - Suite Timeout Elapsed[0m -- [38;5;10m[1m10 Passed[0m | [38;5;9m[1m1 Failed[0m | [38;5;11m[1m1 Pending[0m | [38;5;14m[1m5 Skipped[0m
--- FAIL: TestE2E (3559.72s)
FAIL
Ginkgo ran 1 suite in 1h0m22.390316483s
Test Suite Failed
real 60m22.414s
user 6m31.758s
sys 1m23.240s
make: *** [Makefile:183: e2e] Error 1
Releasing IP claims
ipclaim.ipam.metal3.io "ip-claim-ba37d82e0f1fd930207a609c5241d04eb76eb735" deleted
ipclaim.ipam.metal3.io "workload-ip-claim-b71ef088328c0253ab399bbca88745206e4e1093" 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 ...