CODEWITHSUNDEEP
azure-devopsazure-pipelines
Darren Wood
Darren Wood

Reputation: 1528

The agent request is not running because all potential agents are running other requests

We are running a pipeline that has run successfully for ages. It is failing as of yesterday. We are getting the error

The agent request is not running because all potential agents are running other requests. The agent pool is offline

enter image description here

This stackoverflow solution says I need to run.cmd, but I am not running a self-hosting agent.

We also get this additional error

Failed to get scaleset from Azure with error: No service Endpoint found with Id: xxxx and Scope xxxx

How do I bring the agent back online and is that the solution to fix the error that is preventing the publish/deploy. If not, how do we fix this issue.

Upvotes: 1

Views: 4273

Answers (1)

Bowman Zhu
Bowman Zhu

Reputation: 7186

There are three kinds of icon of agent pool in Azure DevOps.

Microsoft-hosted agent:

enter image description here

Self-hosted agent:

enter image description here

VMSS(Azure Virtual Machine Scale Set):

enter image description here

So the type you are using is VMSS(Azure Virtual Machine Scale Set) pool. This type of agent pool will based on service connection of one of your project or subscription.

So if the machines are in the VMSS, you can try to edit your VMSS pool settings on Azure DevOps side, you can set up another service connection(please make sure the related register app on azure portal side has required permissions to the VMSS).

If no machine instances or the previous instances were been deleted, then the object on DevOps side will not be able to recovery. You can rec-config to a new VMSS or delete the old pool and create a new one.

Upvotes: 1

Related Questions