Ubuntu 22.04 Runner Times Out at 45 minutes When Allocated from Managed DevOps Pool

[msclbu]

Description

Managed DevOps pool runner image ubuntu-22.04:latest cannot run against Azure DevOps Pipelines and always time out after 45 minutes no many how many runners are scaled out.

This was working a couple of days ago.

There seems to be a mismatch where the latest release on GitHub state 20250427.1.1 whereas the Image Version in MDP shows 20250427.1.0 as the latest tag. I am not sure if this is a red herring though.

Platforms affected

• Azure DevOps
• GitHub Actions - Standard Runners
• GitHub Actions - Larger Runners

Runner images affected

• Ubuntu 22.04
• 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

ubuntu-22.04 Latest
MDP Image version: 20250427.1.0

Is it regression?

20250421.2.1

Expected behavior

MDP Image automatically registers with pipeline and runs job.

Actual behavior

Agent status states it is in allocation mode but pipeline times out after 45 minute threshold with error:

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

Repro steps

Connect Managed DevOps pool to ADO project using ubuntu-2204:latest

Run pipeline scoped to this pool.

Job will hang continuously querying agent status and stating it is taking longer than expect to start.

[DergachevE]

Hi @msclbu,
Thanks for reporting this issue to us.
Can you please provide more details:

1. What is the agent version currently used in your agent pool?
2. Have you tried to run other pipelines on this pool? (i.e. different Ubuntu version)
3. Do you observe any errors for agents in pool? You can refer to this docs on how to monitor MDP pools

[msclbu]

Hi @DergachevE

Unfortunately I can't see the agent version due to MDP interpreting it as Azure Hosted Runners.
I'll have a try tomorrow with a windows-2022 runner as I am awaiting for my allotted agent grace period to expire and recycle.
Nothing obvious with metrics and errors.

This could potentially be an issue with MDP backend service itself at this stage rather than the runner, it just felt a bit coincidental due to the recent updated runner.

[vidyasagarnimmagaddi]

HI @msclbu ,

I'll have a try tomorrow with a windows-2022 runner as I am awaiting for my allotted agent grace period to expire and recycle.
Nothing obvious with metrics and errors

Sure, Kindly try to provide the error if any.

[msclbu]

HI @msclbu ,

I'll have a try tomorrow with a windows-2022 runner as I am awaiting for my allotted agent grace period to expire and recycle.
Nothing obvious with metrics and errors

Sure, Kindly try to provide the error if any.

Hi @vidyasagarnimmagaddi,

I have some further test information today plus the agent versions from ADO REST API.

Windows-2022:latest 20250427.1.0 runs successfully and is on ADO Agent 4.255.0

Ubuntu 22-04:latest still times out and is on ADO Agent 4.254.0

Checked previous pipeline runs and last successful was on Wednesday using runner 20250421 - Obviously the new runner image with a bug propagated to AustraliaEast region by the time of the failed runs yesterday.

It is a shame that there is no way to override build number in YAML pipelines when using MS Hosted images in MDP. This means if a runner contains a bug there is no way to rollback and pin a build number until a fix is found. Luckily our pipelines also work in Windows but can see it being an issue if heavily weighed towards Ubuntu 22.04.

[DergachevE]

@msclbu the latest successful build on Ubuntu 22.04 (20250421) - which agent version did it use?
Currently I see 2 options:

• ubuntu image changed
• agent version might be different

[msclbu]

@DergachevE 4.254.0 we are also looking at our FW rules again as to whether they are too strict. It might be the case the last image had enough tolerance to deal with our FW but this image cannot in terms of endpoints it contacts on provisioning.

[st0le]

@msclbu You can use a ImageVersionOverride Demand https://github.com/MicrosoftDocs/azure-devops-docs/blob/main/docs/managed-devops-pools/demands.md#imageoverride

[msclbu]

@st0le that only works for Azure Computer Gallery and Marketplace images. Not MS published runners.

[gakama]

@msclbu Seems like a doc bug. It should work as long as you specify the same Image Version as the one that previously succeeded run. (Check Initialize Job Step for the Exact Version from a previous run)

[msclbu]

@gakama unfortunately doesn't seem to work with MDP. Exception could not find version 20250421.2.0 of the image from the MS subscription that hosts the Compute Gallery.

`demands:

• ImageOverride -equals ubuntu-22.04
• ImageVersionOverride -equals 20250421.2.0`

##[error]Failed to request agent. Exception Could not find version 20250421.2.0 of the image /subscriptions/***/resourceGroups/ManagedDevOpsPools/providers/Microsoft.Compute/galleries/MMSGallery/images/MMSUbuntu22.04/versions/latest