Lab Services - VMs not being created in the machine pool

%3CLINGO-SUB%20id%3D%22lingo-sub-3288858%22%20slang%3D%22en-US%22%3ELab%20Services%20-%20VMs%20not%20being%20created%20in%20the%20machine%20pool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3288858%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBeen%20trying%20to%20create%20new%20VMs%20in%20a%20existing%20lab%20host%20pool%20for%20a%20few%20days.%20They%20are%20all%20sitting%20on%20'Creating..'.%20I%20have%20tried%20to%20increase%20%2F%20decrease%20the%20host%20pool%20size%2C%20removed%20some%20additional%20labs%20as%20well%20as%20removing%20my%20own%20allocated%20VM%20from%20the%20lab.%20Nothing%20has%20changed%20for%20at%20least%202%20days.%20Any%20advice%20welcome.%20I%20have%20already%20check%20the%20logs%20in%20the%20Lab%20Services%20node%20for%20that%20lab%20and%20there%20are%20no%20errors.%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Screenshot%202022-04-19%20140246.jpg%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F365160iEAD4B014738EB950%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22Screenshot%202022-04-19%20140246.jpg%22%20alt%3D%22Screenshot%202022-04-19%20140246.jpg%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3289291%22%20slang%3D%22en-US%22%3ERe%3A%20Lab%20Services%20-%20VMs%20not%20being%20created%20in%20the%20machine%20pool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3289291%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1366816%22%20target%3D%22_blank%22%3E%40LGoldsborough330%3C%2FA%3E%26nbsp%3B-%20When%20labs%20get%20stuck%20in%20a%20%22creating%22%20state%2C%20it%20often%20indicates%20that%20Azure%20Lab%20Services%20is%20unable%20to%20properly%20allocate%20VMs%20to%20your%20lab.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20would%20recommend%20logging%20a%20support%20ticket%20so%20that%20we%20can%20ensure%20that%20your%20subscrition%5Clabs%20are%20able%20allocate%20the%20number%20of%20VMs%20for%20the%20VM%20size%20and%20region(s)%20that%20you%20need.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhile%20I%20recommend%20logging%20a%20support%20ticket%2C%20another%20option%20you%20could%20also%20try%20is%20deleting%5Crecreating%20the%20lab%20which%20may%20automatically%20resolve%20the%20issue%20you're%20seeing.%26nbsp%3B%20Also%2C%20if%20your%20lab%20is%20large%20(such%20100%2B%20VMs)%2C%20you%20may%20also%20restructure%20the%20lab%20into%20several%20labs%20that%20have%20a%20smaller%20number%20of%20VMs%20in%20each%20one.%26nbsp%3B%20For%20example%2C%20instead%20of%20having%20a%20lab%20with%20100%20VMs%2C%20you%20could%20create%20two%20labs%20each%20with%2050%20VMs.%26nbsp%3B%20These%20options%20work%20best%20when%20your%20labs%20aren't%20using%20VNet%20peering%20(which%20ties%20you%20to%20a%20specific%20region)%20-%20if%20you're%20not%20using%20VNet%20peering%2C%20Azure%20Labs%20has%20greater%20flexibility%20to%20allocate%20VMs%20to%20you%20within%20any%20region%20of%20your%20Lab%20Account's%20location%5Cgeography.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%2C%3CBR%20%2F%3ENicole%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

Hi,

 

Been trying to create new VMs in a existing lab host pool for a few days. They are all sitting on 'Creating..'. I have tried to increase / decrease the host pool size, removed some additional labs as well as removing my own allocated VM from the lab. Nothing has changed for at least 2 days. Any advice welcome. I have already check the logs in the Lab Services node for that lab and there are no errors.
Screenshot 2022-04-19 140246.jpg

1 Reply

@LGoldsborough330 - When labs get stuck in a "creating" state, it often indicates that Azure Lab Services is unable to properly allocate VMs to your lab.

 

I would recommend logging a support ticket so that we can ensure that your subscrition\labs are able allocate the number of VMs for the VM size and region(s) that you need.

 

While I recommend logging a support ticket, another option you could also try is deleting\recreating the lab which may automatically resolve the issue you're seeing.  Also, if your lab is large (such 100+ VMs), you may also restructure the lab into several labs that have a smaller number of VMs in each one.  For example, instead of having a lab with 100 VMs, you could create two labs each with 50 VMs.  These options work best when your labs aren't using VNet peering (which ties you to a specific region) - if you're not using VNet peering, Azure Labs has greater flexibility to allocate VMs to you within any region of your Lab Account's location\geography.

 

Thanks,
Nicole