[JIRA] (JENKINS-57204) Provision failures does not clean up deployments

[rty...@brokenco.de (JIRA)]

Title: Message Title

R. Tyler Croy created an issue   Jenkins / JENKINS-57204 Provision failures does not clean up deployments Issue Type: Bug Assignee: Azure DevOps Components: azure-container-agents-plugin Created: 2019-04-27 15:26 Priority: Critical Reporter: R. Tyler Croy We're seeing a number of failures on ci.jenkins.io which stem from Azure Container Agents failing to provision. It looks like failed ACI deployments don't get cleaned up automatically by the plugin. ACI is returning the following failure: {"code":"DeploymentFailed","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.","details":[{"code":"Conflict","message":"{\r\n \"error\": {\r\n \"code\": \"ServiceUnavailable\",\r\n \"message\": \"The requested resource is not available in the location 'eastus2' at this moment. Please retry with a different resource request or in another location. Resource requested: '2' CPU '4' GB memory 'Linux' OS\"\r\n }\r\n}"}]} Which is annoying, but whatever. The bug here is that the plugin does not clean up this failed deployment, so we have exceeded our quota of Deployments of 800, all failures like this one! I recall this exact same issue in the Azure VM Agents plugin at one point as well. 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. For more options, visit https://groups.google.com/d/optout.