This job view page is being replaced by Spyglass soon. Check out the new job view.
ResultFAILURE
Tests 0 failed / 0 succeeded
Started2023-01-26 05:20
Elapsed1h4m
Revisionmain

No Test Failures!

Error lines from build-log.txt

... skipping 617 lines ...
  INFO: Waiting for the machine deployments to be provisioned
  STEP: Waiting for the workload nodes to exist @ 01/26/23 05:35:36.062
  STEP: Checking all the machines controlled by quick-start-64wr9q-md-0-8rwkw are in the "<None>" failure domain @ 01/26/23 05:37:06.176
  INFO: Waiting for the machine pools to be provisioned
  STEP: PASSED! @ 01/26/23 05:37:06.215
  STEP: Dumping logs from the "quick-start-64wr9q" workload cluster @ 01/26/23 05:37:06.215
Failed to get logs for Machine quick-start-64wr9q-md-0-8rwkw-798d774b4b-kk7k4, Cluster quick-start-h306cd/quick-start-64wr9q: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine quick-start-64wr9q-qhvzz-7jfm5, Cluster quick-start-h306cd/quick-start-64wr9q: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
  STEP: Dumping all the Cluster API resources in the "quick-start-h306cd" namespace @ 01/26/23 05:37:10.624
  STEP: Deleting cluster quick-start-h306cd/quick-start-64wr9q @ 01/26/23 05:37:10.921
  STEP: Deleting cluster quick-start-64wr9q @ 01/26/23 05:37:10.938
  INFO: Waiting for the Cluster quick-start-h306cd/quick-start-64wr9q to be deleted
  STEP: Waiting for cluster quick-start-64wr9q to be deleted @ 01/26/23 05:37:10.952
  STEP: Deleting namespace used for hosting the "quick-start" test spec @ 01/26/23 05:37:40.973
... skipping 44 lines ...
  INFO: Waiting for the machine deployments to be provisioned
  STEP: Waiting for the workload nodes to exist @ 01/26/23 05:40:12.279
  STEP: Checking all the machines controlled by quick-start-orlf2e-md-0 are in the "<None>" failure domain @ 01/26/23 05:41:32.372
  INFO: Waiting for the machine pools to be provisioned
  STEP: PASSED! @ 01/26/23 05:41:32.427
  STEP: Dumping logs from the "quick-start-orlf2e" workload cluster @ 01/26/23 05:41:32.427
Failed to get logs for Machine quick-start-orlf2e-7n6bk, Cluster quick-start-abxnl7/quick-start-orlf2e: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine quick-start-orlf2e-md-0-79f74b78cf-md5zw, Cluster quick-start-abxnl7/quick-start-orlf2e: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
  STEP: Dumping all the Cluster API resources in the "quick-start-abxnl7" namespace @ 01/26/23 05:41:36.87
  STEP: Deleting cluster quick-start-abxnl7/quick-start-orlf2e @ 01/26/23 05:41:37.189
  STEP: Deleting cluster quick-start-orlf2e @ 01/26/23 05:41:37.215
  INFO: Waiting for the Cluster quick-start-abxnl7/quick-start-orlf2e to be deleted
  STEP: Waiting for cluster quick-start-orlf2e to be deleted @ 01/26/23 05:41:37.229
  STEP: Deleting namespace used for hosting the "quick-start" test spec @ 01/26/23 05:42:07.248
... skipping 101 lines ...
  INFO: Waiting for the machine deployments to be provisioned
  STEP: Waiting for the workload nodes to exist @ 01/26/23 05:48:42.59
  STEP: Checking all the machines controlled by quick-start-lv16zk-md-0 are in the "<None>" failure domain @ 01/26/23 05:49:42.661
  INFO: Waiting for the machine pools to be provisioned
  STEP: PASSED! @ 01/26/23 05:49:42.709
  STEP: Dumping logs from the "quick-start-lv16zk" workload cluster @ 01/26/23 05:49:42.709
Failed to get logs for Machine quick-start-lv16zk-dcqcs, Cluster quick-start-6d8afk/quick-start-lv16zk: dialing host IP address at 192.168.6.110: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
Failed to get logs for Machine quick-start-lv16zk-md-0-5bc688bfb7-hhbhv, Cluster quick-start-6d8afk/quick-start-lv16zk: dialing host IP address at 192.168.6.63: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain
  STEP: Dumping all the Cluster API resources in the "quick-start-6d8afk" namespace @ 01/26/23 05:49:45.205
  STEP: Deleting cluster quick-start-6d8afk/quick-start-lv16zk @ 01/26/23 05:49:45.485
  STEP: Deleting cluster quick-start-lv16zk @ 01/26/23 05:49:45.501
  INFO: Waiting for the Cluster quick-start-6d8afk/quick-start-lv16zk to be deleted
  STEP: Waiting for cluster quick-start-lv16zk to be deleted @ 01/26/23 05:49:45.512
  STEP: Deleting namespace used for hosting the "quick-start" test spec @ 01/26/23 05:50:15.53
... skipping 105 lines ...
  INFO: Waiting for correct number of replicas to exist
  STEP: Scaling the MachineDeployment down to 1 @ 01/26/23 05:59:10.581
  INFO: Scaling machine deployment md-scale-tt4mrr/md-scale-6pxkzg-md-0 from 3 to 1 replicas
  INFO: Waiting for correct number of replicas to exist
  STEP: PASSED! @ 01/26/23 05:59:20.688
  STEP: Dumping logs from the "md-scale-6pxkzg" workload cluster @ 01/26/23 05:59:20.688
Failed to get logs for Machine md-scale-6pxkzg-9vmlm, Cluster md-scale-tt4mrr/md-scale-6pxkzg: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
Failed to get logs for Machine md-scale-6pxkzg-md-0-86f64cb7c7-sp5js, Cluster md-scale-tt4mrr/md-scale-6pxkzg: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
  STEP: Dumping all the Cluster API resources in the "md-scale-tt4mrr" namespace @ 01/26/23 05:59:25.026
  STEP: Deleting cluster md-scale-tt4mrr/md-scale-6pxkzg @ 01/26/23 05:59:25.305
  STEP: Deleting cluster md-scale-6pxkzg @ 01/26/23 05:59:25.321
  INFO: Waiting for the Cluster md-scale-tt4mrr/md-scale-6pxkzg to be deleted
  STEP: Waiting for cluster md-scale-6pxkzg to be deleted @ 01/26/23 05:59:25.333
  STEP: Deleting namespace used for hosting the "md-scale" test spec @ 01/26/23 05:59:55.351
... skipping 57 lines ...
  INFO: Waiting for MachineDeployment rollout for MachineDeploymentTopology "md-0" (class "quick-start-worker") to complete.
  STEP: Deleting a MachineDeploymentTopology in the Cluster Topology and wait for associated MachineDeployment to be deleted @ 01/26/23 06:04:27.068
  INFO: Removing MachineDeploymentTopology from the Cluster Topology.
  INFO: Waiting for MachineDeployment to be deleted.
  STEP: PASSED! @ 01/26/23 06:04:37.14
  STEP: Dumping logs from the "clusterclass-changes-396fr3" workload cluster @ 01/26/23 06:04:37.14
Failed to get logs for Machine clusterclass-changes-396fr3-5mc2k-vkdgm, Cluster clusterclass-changes-i8lted/clusterclass-changes-396fr3: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
  STEP: Dumping all the Cluster API resources in the "clusterclass-changes-i8lted" namespace @ 01/26/23 06:04:39.31
  STEP: Deleting cluster clusterclass-changes-i8lted/clusterclass-changes-396fr3 @ 01/26/23 06:04:39.597
  STEP: Deleting cluster clusterclass-changes-396fr3 @ 01/26/23 06:04:39.614
  INFO: Waiting for the Cluster clusterclass-changes-i8lted/clusterclass-changes-396fr3 to be deleted
  STEP: Waiting for cluster clusterclass-changes-396fr3 to be deleted @ 01/26/23 06:04:39.625
  STEP: Deleting namespace used for hosting the "clusterclass-changes" test spec @ 01/26/23 06:04:59.641
... skipping 122 lines ...
  STEP: Waiting for deployment node-drain-o45ig0-unevictable-workload/unevictable-pod-cbv to be available @ 01/26/23 06:20:07.483
  STEP: Scale down the controlplane of the workload cluster and make sure that nodes running workload can be deleted even the draining process is blocked. @ 01/26/23 06:20:17.86
  INFO: Scaling controlplane node-drain-o45ig0/node-drain-rbtkqi from 3 to 1 replicas
  INFO: Waiting for correct number of replicas to exist
  STEP: PASSED! @ 01/26/23 06:24:18.47
  STEP: Dumping logs from the "node-drain-rbtkqi" workload cluster @ 01/26/23 06:24:18.47
Failed to get logs for Machine node-drain-rbtkqi-qsf7m, Cluster node-drain-o45ig0/node-drain-rbtkqi: running command "cat /var/log/cloud-init-output.log": Process exited with status 1
  STEP: Dumping all the Cluster API resources in the "node-drain-o45ig0" namespace @ 01/26/23 06:24:20.478
  STEP: Deleting cluster node-drain-o45ig0/node-drain-rbtkqi @ 01/26/23 06:24:20.758
  STEP: Deleting cluster node-drain-rbtkqi @ 01/26/23 06:24:20.774
  INFO: Waiting for the Cluster node-drain-o45ig0/node-drain-rbtkqi to be deleted
  STEP: Waiting for cluster node-drain-rbtkqi to be deleted @ 01/26/23 06:24:20.788
  STEP: Deleting namespace used for hosting the "node-drain" test spec @ 01/26/23 06:24:50.814
... skipping 116 lines ...
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc002690570, 0x28}, {0xc0026905a0, 0x23}, {0xc0020d1d14, 0xb}, ...}, ...}, ...)
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186
              | out := bufio.NewWriter(f)
              | defer out.Flush()
              > _, err = out.ReadFrom(podLogs)
              | if err != nil && err != io.ErrUnexpectedEOF {
              | 	// Failing to stream logs should not cause the test to fail
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161
              | 
              | // Watch each container's logs in a goroutine so we can stream them all concurrently.
              > go func(pod corev1.Pod, container corev1.Container) {
              | 	defer GinkgoRecover()
... skipping 21 lines ...
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc000d707c0, 0x3a}, {0xc000d70800, 0x35}, {0xc00113edc0, 0x1d}, ...}, ...}, ...)
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186
              | out := bufio.NewWriter(f)
              | defer out.Flush()
              > _, err = out.ReadFrom(podLogs)
              | if err != nil && err != io.ErrUnexpectedEOF {
              | 	// Failing to stream logs should not cause the test to fail
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161
              | 
              | // Watch each container's logs in a goroutine so we can stream them all concurrently.
              > go func(pod corev1.Pod, container corev1.Container) {
              | 	defer GinkgoRecover()
... skipping 6 lines ...
              | for {
              > 	select {
              | 	case <-ctx.Done():
              | 		return
        > sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225
              | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment))
              | 
              > go func() {
              | 	defer GinkgoRecover()
              | 	for {

        goroutine 33163 [select]
... skipping 3 lines ...
              | for {
              > 	select {
              | 	case <-ctx.Done():
              | 		return
        > sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225
              | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment))
              | 
              > go func() {
              | 	defer GinkgoRecover()
              | 	for {

        goroutine 33157 [select]
... skipping 3 lines ...
              | for {
              > 	select {
              | 	case <-ctx.Done():
              | 		return
        > sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225
              | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment))
              | 
              > go func() {
              | 	defer GinkgoRecover()
              | 	for {

        goroutine 33167 [sync.Cond.Wait]
... skipping 18 lines ...
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc002307e90, 0x27}, {0xc002307ec0, 0x22}, {0xc0021983b4, 0xb}, ...}, ...}, ...)
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186
              | out := bufio.NewWriter(f)
              | defer out.Flush()
              > _, err = out.ReadFrom(podLogs)
              | if err != nil && err != io.ErrUnexpectedEOF {
              | 	// Failing to stream logs should not cause the test to fail
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161
              | 
              | // Watch each container's logs in a goroutine so we can stream them all concurrently.
              > go func(pod corev1.Pod, container corev1.Container) {
              | 	defer GinkgoRecover()
... skipping 29 lines ...
              | for {
              > 	select {
              | 	case <-ctx.Done():
              | 		return
        > sigs.k8s.io/cluster-api/test/framework.WatchPodMetrics
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:225
              | }, retryableOperationTimeout, retryableOperationInterval).Should(Succeed(), "Failed to list Pods for deployment %s", klog.KObj(input.Deployment))
              | 
              > go func() {
              | 	defer GinkgoRecover()
              | 	for {

        goroutine 33160 [sync.Cond.Wait]
... skipping 18 lines ...
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs.func2({{{0x0, 0x0}, {0x0, 0x0}}, {{0xc0017bdfc0, 0x3e}, {0xc000dcc000, 0x39}, {0xc000cab3e0, 0x21}, ...}, ...}, ...)
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:186
              | out := bufio.NewWriter(f)
              | defer out.Flush()
              > _, err = out.ReadFrom(podLogs)
              | if err != nil && err != io.ErrUnexpectedEOF {
              | 	// Failing to stream logs should not cause the test to fail
        > sigs.k8s.io/cluster-api/test/framework.WatchDeploymentLogs
            /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/framework/deployment_helpers.go:161
              | 
              | // Watch each container's logs in a goroutine so we can stream them all concurrently.
              > go func(pod corev1.Pod, container corev1.Container) {
              | 	defer GinkgoRecover()
... skipping 17 lines ...

Summarizing 1 Failure:
  [TIMEDOUT] When testing unhealthy machines remediation [It] Should successfully trigger machine deployment remediation
  /home/prow/go/pkg/mod/sigs.k8s.io/cluster-api/test@v1.3.0/e2e/mhc_remediations.go:83

Ran 11 of 17 Specs in 3549.280 seconds
FAIL! - Suite Timeout Elapsed -- 10 Passed | 1 Failed | 1 Pending | 5 Skipped
--- FAIL: TestE2E (3549.28s)
FAIL

Ginkgo ran 1 suite in 1h0m1.649830138s

Test Suite Failed

real	60m1.671s
user	5m35.048s
sys	1m9.936s
make: *** [Makefile:183: e2e] Error 1
Releasing IP claims
ipclaim.ipam.metal3.io "ip-claim-e2958bff89554bbd76eed47dd7223f04d73cc81f" deleted
ipclaim.ipam.metal3.io "workload-ip-claim-833459cd45e57a97571a01b1f08945670df6331a" 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 ...