Ubuntu 22.04 Runner Times Out At 45 Minutes When Allocated From Managed DevOps Pool

by ADMIN 84 views

Introduction

Ubuntu 22.04 is a popular Linux distribution used in various environments, including Azure DevOps Pipelines. However, users have reported an issue where the Ubuntu 22.04 runner times out after 45 minutes when allocated from a Managed DevOps pool. This issue has been observed in Azure DevOps, and it is essential to understand the root cause and potential solutions to resolve this problem.

Description of the Issue

The issue is that the Ubuntu 22.04 runner image, which is the latest version available on GitHub, cannot run against Azure DevOps Pipelines. The runner times out after 45 minutes, regardless of the number of runners scaled out. This issue has been reported by users, and it is essential to investigate the cause and potential solutions.

Platforms Affected

The issue is specific to Azure DevOps and affects the Ubuntu 22.04 runner image. The following platforms are not affected:

  • GitHub Actions - Standard Runners
  • GitHub Actions - Larger Runners

Runner Images Affected

The issue is specific to the Ubuntu 22.04 runner image. The following runner images are not affected:

  • Ubuntu 24.04
  • macOS 13
  • macOS 13 Arm64
  • macOS 14
  • macOS 14 Arm64
  • macOS 15
  • macOS 15 Arm64
  • Windows Server 2019
  • Windows Server 2022
  • Windows Server 2025

Image Version and Build Link

The Ubuntu 22.04 runner image is the latest version available on GitHub, which is 20250427.1.1. However, the Image Version in the Managed DevOps pool shows 20250427.1.0 as the latest tag. This discrepancy may be a red herring, but it is essential to investigate further.

Is it a Regression?

The issue was not present a couple of days ago, which suggests that it may be a regression. The previous version of the Ubuntu 22.04 runner image, which was 20250421.2.1, did not exhibit this issue.

Expected Behavior

The expected behavior is that the Managed DevOps pool image automatically registers with the pipeline and runs the job. However, the actual behavior is that the agent status states it is in allocation mode, but the pipeline times out after 45 minutes with an error message.

Actual Behavior

The actual behavior is that the pipeline times out after 45 minutes with an error message:

"The agent did not connect within the alloted time of 45 minute(s)."

Repro Steps

To reproduce the issue, follow these steps:

  1. Connect the Managed DevOps pool to the Azure DevOps project using the ubuntu-2204:latest image.
  2. Run the pipeline scoped to this pool.
  3. The job will hang continuously querying the agent status and stating it is taking longer than expected to start.

Potential Solutions

To resolve this issue, the following potential solutions can be explored:

  1. Update the Image Version: Update the Image Version in the Managed DevOps pool to the latest version available on GitHub, which is 20250427.1.1.
  2. Check the Runner Image: Check the runner image for any issues or bugs that may be causing the timeout.
  3. Investigate the Pipeline: Investigate the pipeline for any issues or bugs that may be causing the timeout.
  4. Contact Support: Contact Azure DevOps support for further assistance and guidance.

Conclusion

Introduction

In our previous article, we discussed the issue of the Ubuntu 22.04 runner times out after 45 minutes when allocated from a Managed DevOps pool in Azure DevOps. In this article, we will provide a Q&A section to address some of the frequently asked questions related to this issue.

Q: What is the root cause of the issue?

A: The root cause of the issue is not yet clear, but it is believed to be related to a discrepancy between the Image Version in the Managed DevOps pool and the latest version available on GitHub.

Q: Why is the Ubuntu 22.04 runner image affected?

A: The Ubuntu 22.04 runner image is affected because it is the latest version available on GitHub, and the Image Version in the Managed DevOps pool is not updated to the latest version.

Q: What are the potential solutions to resolve the issue?

A: The potential solutions to resolve the issue include:

  1. Update the Image Version: Update the Image Version in the Managed DevOps pool to the latest version available on GitHub.
  2. Check the Runner Image: Check the runner image for any issues or bugs that may be causing the timeout.
  3. Investigate the Pipeline: Investigate the pipeline for any issues or bugs that may be causing the timeout.
  4. Contact Support: Contact Azure DevOps support for further assistance and guidance.

Q: How can I update the Image Version in the Managed DevOps pool?

A: To update the Image Version in the Managed DevOps pool, follow these steps:

  1. Go to the Azure DevOps project and navigate to the Managed DevOps pool.
  2. Click on the "Images" tab and select the Ubuntu 22.04 runner image.
  3. Click on the "Update" button and select the latest version available on GitHub.
  4. Click on the "Save" button to save the changes.

Q: What are the benefits of updating the Image Version in the Managed DevOps pool?

A: The benefits of updating the Image Version in the Managed DevOps pool include:

  1. Improved performance: Updating the Image Version can improve the performance of the pipeline by ensuring that the latest version of the runner image is used.
  2. Reduced downtime: Updating the Image Version can reduce downtime by ensuring that the pipeline is always running with the latest version of the runner image.
  3. Enhanced security: Updating the Image Version can enhance security by ensuring that the pipeline is always running with the latest version of the runner image, which may include security patches and updates.

Q: How can I check the runner image for any issues or bugs?

A: To check the runner image for any issues or bugs, follow these steps:

  1. Go to the Azure DevOps project and navigate to the Managed DevOps pool.
  2. Click on the "Images" tab and select the Ubuntu 22.04 runner image.
  3. Click on the "Details" button to view the details of the runner image.
  4. Check the "Issues" and "Bugs" sections to see if there are any known issues or bugs with the runner image.

Q: How can I investigate the pipeline for any issues or bugs?

A: To investigate the pipeline for any issues or bugs, follow these steps:

  1. Go to the Azure DevOps project and navigate to the pipeline.
  2. Click on the "Pipeline" tab and select the pipeline that is experiencing issues.
  3. Click on the "Details" button to view the details of the pipeline.
  4. Check the "Issues" and "Bugs" sections to see if there are any known issues or bugs with the pipeline.

Conclusion

In this Q&A article, we have addressed some of the frequently asked questions related to the issue of the Ubuntu 22.04 runner times out after 45 minutes when allocated from a Managed DevOps pool in Azure DevOps. We hope that this article has provided valuable information and insights to help users resolve this issue.