For whichever reason the worker is failing to serve the logs to the bastion, giving a timeout instead, tried rebooting it and such but it did not help.
It blocks the deployment as it makes the tests fail.
toolsbeta.test@toolsbeta-bastion-7:~$ toolforge build start https://gitlab.wikimedia.org/toolforge-repos/wm-lol Waiting for the logs... if the build just started this might take a minute BuildClientError: Error getting the logs for test-buildpacks-pipelinerun-85l2k: Get "https://172.16.5.174:10250/containerLogs/image-build/test-buildpacks-pipelinerun-85l2k-build-from-git-pod/prepare?follow=true×tamps=true": dial tcp 172.16.5.174:10250: i/o timeout Please report this issue to the Toolforge admins if it persists: https://w.wiki/6Zuu
dcaro@toolsbeta-bastion-7:~$ kubectl-sudo logs -n alloy alloy-2js27 Error from server: Get "https://172.16.5.174:10250/containerLogs/alloy/alloy-2js27/alloy": dial tcp 172.16.5.174:10250: i/o timeout
Will remove and recreate.