Tim Jacomb

Built a snapshot plugin based on https://github.com/jenkinsci/azure-vm-agents-plugin/commit/82829b83854244c8e203e67fff7689056a8fd515 Upload the azure-vm-agents.hpi, then restart Jenkins. Check the new pic I uploaded.  It is the same error. See new attached pic.  From jenkins...

Oops, please ignore my last comment. Even the same error appears, but the vm provisioned successfully this time. I saw it in the jenkins agent list. However, Cloud Statistics report...

With more testing, I config the max vm nunmber is 4 which the pool size is 1. I submit a branch of requests to trigger it. As it thinks test-vm407940 ...

Jie, do we have a fix for this? Jie Shen by diwang

di wang I have tested with vnet configuration(delete and provision several times), but I still get no luck to reproduce your error. I use the latest version on the dev...

For provisioning more nodes than the limits, it is an existing issue GH-56972 caused by bad concurrency control. I will try to fix this later. by jieshe

I think solved, given no feedback since 2019

Thanks for your suggestion. I will figure out whether it is suitable to achieve this for this plugin. by jieshe

 Thanks for reporting this issue. I am trying to reproduce it on my side. by jieshe

Hi. One more thing that might be relevant - I'm using managed identity (system created) by rsikora