[JIRA] (JENKINS-41568) Failing to provision new agents despite not being at maxumum

[ty...@monkeypox.org (JIRA)]

Title: Message Title

R. Tyler Croy created an issue   Jenkins / JENKINS-41568 Failing to provision new agents despite not being at maxumum Issue Type: Bug Assignee: Claudiu Guiman Attachments: Selection_062.png Components: azure-vm-agents-plugin Created: 2017/Jan/30 5:03 PM Priority: Minor Reporter: R. Tyler Croy See the attached screenshot. I'm not sure how I ended up getting into this state. Here's what I do know: There are not 16 VMs provisioned in this environment despite the System Log claiming there are. There have been recent ARM deployment errors for one of my VM templates: { "status": "Failed", "error": { "code": "ResourceDeploymentFailure", "message": "The resource operation completed with terminal provisioning state 'Failed'.", "details": [ { "code": "VMExtensionProvisioningTimeout", "message": "Provisioning of VM extension 'customScriptwin2012-110340' has timed out. Extension installation may be taking too long, or extension status could not be obtained." } ] } } { "error": { "code": "ResourceNotFound", "message": "The Resource 'Microsoft.Compute/virtualMachines/win2012-a13100/extensions/customScriptwin2012-a13100' under resource group 'jenkinsinfra-vmagents' was not found." } } { "error": { "code": "NotFound", "target": "vmName", "message": "The entity was not found." } } My theory is that the template failed to fully initialize, but was counted as a provisioned VM within the plugin's tracking of these things. Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.