Bitbucket self-hosted runner does not show all steps

Question

I have multiple runners on two hosts. I have a pipeline with several steps. One of those steps runs several minutes and creates a lot of output (Docker build).

Runners on both hosts run the pipeline successfully according to the UI. However, if the pipeline runs on a runner of host 1, the UI shows no steps after the long running step and its related output is incomplete (cut at the end), even though "Build teardown" is shown. If the pipeline runs on a runner of host 2, the UI shows all steps of the pipeline with the related output of the command.

Besides, all steps are executed on both hosts, since the step after the long running step creates (and pushs) a new Git branch that exists after the pipeline finished. It does not matter which runner on a host is used. All runners on host 1 have the same issue. All runners run version 1.559.

I already recreated all runners. I had the same issue with older versions of the runner. I had hoped that an update of the runner version may help, but that wasn't the case.

Theodora Boudale · Answer

Hi @maiermic,

Thank you for the info. I think it's best to create a support ticket then for further troubleshooting.

If you have a workspace on Standard or Premium billing plan, you can create a ticket via https://support.atlassian.com/contact/#/, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product. When you are asked to provide the workspace URL, please make sure you enter the URL of the workspace that is on a paid billing plan to proceed with ticket creation. Please also provide the URL to relevant builds.

If all your workspaces are on the Free plan, please let me know and I can create the ticket for you. I need to create the ticket though using the email of the Bitbucket account that has access to the repos and builds. The Bitbucket account with the same email as this community account of yours doesn't have write or admin access to any repos, so I'm not sure if you have another Bitbucket account with a different email. If you do, please log in to community with that other email and leave a reply here (if you leave a reply, I can see the account's email).

Kind regards,
Theodora

maiermic · Answer

Docker Root Dir: /var/lib/docker

I'm not sure, when the issue started. It might have been caused by a update of the host. Docker was not reinstalled. I don't remember if it always occured. I can't rule it out. Unfortunately, I can't check it anymore.

We do run other pipelines on host 1. Actually, our pipelines are not tied to a specific host. That made it troublesome to find out the culprit. It was only after I activated the hosts separately that I was able to confirm my suspicion.

However, we should not forget, that each step might be run by a different runner (e.g. host). Besides the missing output in the last shown step that is run on host 1, I can't tell, which host runs the steps afterwards, since they are not shown.

Theodora Boudale · Answer

Hi @maiermic,

* If you run the command docker info on the affected host 1, is the Docker Root Dir in the output the default one, /var/lib/docker? Or have you perhaps changed this? I saw that another customer reported a similar issue and the culprit was that the Docker Root Dir was different than the default one.

* Did this issue appear recently, after a certain update on this machine for example? Or after a reinstallation of Docker? Or has it always been occurring?

* Do you run any other pipelines on host 1 (different than the affected pipeline) and do they have the same issue as well? I would like to understand if the issue is specific to that certain pipeline or not.

Kind regards,
Theodora