How to debug azure vm agent provisioning failure?
In current Jenkin server, most of the slave nodes are configured in Jenkins as Microsoft Azure VM Agents, when a build is trigger to run on slave node, it will first provision a vm agent with the specified slave label name, however, sometimes we will encounter issue that the slave vm agent is created but never connects to Jenkins successfully as an online slave.
In Azure Resource Group Deployments
we can click on Operation details to view errors in detail. And you can check error code in https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-common-deployment-errors
Inside the machine, we can see logs to download and execute initialize script under C:\Packages
Initialize script will be downloaded to C:\Packages\Plugins\Microsoft.Compute.CustomScriptExtension<plugin version>\Downloads\0
Initialize script running result will be saved to C:\Packages\Plugins\Microsoft.Compute.CustomScriptExtension<plugin version>\Status
Detail custom script extension installation logs will be found at C:\WindowsAzure\Logs\Plugins\Microsoft.Compute.CustomScriptExtension<plugin version>
Other azure agent logs can be found at C:\WindowsAzure\Logs