We are currently using the Azure VM agents plugin for our CI/CD environment, we use custom images.

Our images are one of:

• Image 1
  • Linux (With SSH launch)
  • Idle retention time (10 min)
  • Shutdown Only enabled
• Image 2
  • Windows (With JNLP launch)
  • Idle retention time (20 min)
  • Shutdown Only enabled

Our issue is that we have an agent that successfully gets provisioned launched and is usable, after the idle timeout the node successfully shuts down and applies the (offline) and (suspended) flags to it correctly. Once another build comes along and attempts to use it, the plugin correctly launches the previously shutdown VM it starts correctly, connects correctly but it maintains the (suspended) flag making it unusable. I can manually fix it by issuing the following command in the Jenkins script console

Jenkins.instance.getNode('azure-nodeXXXXXX').toComputer().setAcceptingTasks(true);

Then the build goes to the node and builds successfully, however if that command is not issued the build gets stuck waiting for the node to come online.

This issue happens with both types of images.