[JIRA] (JENKINS-58861) Plugin believes the quota has been reached when no nodes are present.
Title: Message Title Jie Shen commented on JENKINS-58861 Re: Plugin believes the quota has been reached when no nodes are present. Could you please provide some specific error message? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201176.1565276471000.2.1565321940238%40Atlassian.JIRA.
[JIRA] (JENKINS-58861) Plugin believes the quota has been reached when no nodes are present.
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-58861 Plugin believes the quota has been reached when no nodes are present. Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201176.1565276471000.0.1565321580307%40Atlassian.JIRA.
[JIRA] (JENKINS-58861) Plugin believes the quota has been reached when no nodes are present.
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-58861 Plugin believes the quota has been reached when no nodes are present. Issue Type: Bug Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2019-08-08 15:01 Environment: Jenkins LTS 2.176.22 Azure VM agents plugin 1.1.1 Priority: Major Reporter: R. Tyler Croy We noticed this behavior on ci.jenkins.io where a number of agents failed to provision due to timeout errors in the Azure API. The resource group was filled with VMs but there were not corresponding agents listed in Jenkins. Looking at the logs I noticed that the instance was complaining that it could not provision more machines due to the quota, despite very few agents actually being listed under /computer. After deleting the resource group in question, Jenkins started provisioning new agents while still complaining about the quota in the logs. I have no idea what happened here, but it seemed like the Azure timeout exceptions accumulated and caused some error condition with managing the quota.
