azure hosted agent| devops | azure pipeline| virtual machine scaleset

Question

Hi there,

I am testing the Azure DevOps environment, and I created a virtual machine scale-set to execute my build pipeline, but what is very odd is that I created the pool based on Microsoft instruction, but when I go to check the agent to see the instance, there is no instance appeared however when I check on azure portal | virtual machine scale set they are already there.

When I commit and run the pipeline, it gives me this error "The agent request is not running because all potential agents are running other requests. Current position in queue: 1

No agents in pool hostedself are currently able to service this request." do you have any idea what is the issue?

Thanks in advance,

Answer 1

@barzan muhammed

Azure Devops is not currently supported here on Microsoft QnA.

The Community Members and Engineers are actively answering questions in dedicated forums here. Please post your question in that forum:

https://developercommunity.visualstudio.com/spaces/21/index.html

https://azure.microsoft.com/en-in/support/devops/

I found some potential causes and solutions. Please check to see if these help:

• One possible cause of this issue is that you created the virtual machine scale-set with the Flexible orchestration mode, which is not supported by Azure Pipelines. You need to create the scale set with the Uniform orchestration mode, which allows Azure Pipelines to manage the scaling and provisioning of the agents. You can find more details on how to create the scale set with the Uniform mode in this article.
• Another possible cause of this issue is that you have set the Maximum number of virtual machines in the scale set to a value that is too low or too high for your workload. You can adjust this setting in Azure DevOps -> Agent pools -> choose your target VMSS agent pool -> Settings. You may need to experiment with different values to find the optimal balance between performance and cost. You can find more details on how to configure the scale set agent pool settings in this answer.
• A third possible cause of this issue is that you have associated the same virtual machine scale-set to multiple agent pools, which can cause conflicts and errors. You should only associate a VMSS to one agent pool at a time. If you have accidentally associated a VMSS to multiple pools, you can fix this by deleting the tags from the scale set in the Azure Portal. You can find more details on how to do this in this answer.

Hope this helps. If you still have issues please reachout to the DevOps community.

---

If you still have questions, please let us know in the "comments" and we would be happy to help you. Comment is the fastest way of notifying the experts. If the answer has been helpful, we appreciate hearing from you and would love to help others who may have the same question. Accepting answers helps increase visibility of this question for other members of the Microsoft Q&A community. Thank you for helping to improve Microsoft Q&A!