[JIRA] (JENKINS-56824) VMs not cleaned up per retention policy when they are in a failed provisioning state.
Title: Message Title Jie Shen commented on JENKINS-56824 Re: VMs not cleaned up per retention policy when they are in a failed provisioning state. Some feedback here. Idle retention policy will not delete offline VMs to avoid deleting temporarily disconnected one. So the issue should be related with why not the VMs being deleted immediately if the init scripts failed. 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.
[JIRA] (JENKINS-56824) VMs not cleaned up per retention policy when they are in a failed provisioning state.
Title: Message Title R. Tyler Croy commented on JENKINS-56824 Re: VMs not cleaned up per retention policy when they are in a failed provisioning state. Unfortunately I don't have a strong reproduction case, just behavior observed in production 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.
[JIRA] (JENKINS-56824) VMs not cleaned up per retention policy when they are in a failed provisioning state.
Title: Message Title Jie Shen updated an issue Jenkins / JENKINS-56824 VMs not cleaned up per retention policy when they are in a failed provisioning state. Change By: Jie Shen Priority: Minor Major 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.
[JIRA] (JENKINS-56824) VMs not cleaned up per retention policy when they are in a failed provisioning state.
Title: Message Title Jie Shen commented on JENKINS-56824 Re: VMs not cleaned up per retention policy when they are in a failed provisioning state. Thanks R. Tyler Croy, this is should be a bug. I will find out how to fix it. 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.
[JIRA] (JENKINS-56824) VMs not cleaned up per retention policy when they are in a failed provisioning state.
Title: Message Title Azure DevOps assigned an issue to Jie Shen Jenkins / JENKINS-56824 VMs not cleaned up per retention policy when they are in a failed provisioning state. Change By: Azure DevOps 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56824) VMs not cleaned up per retention policy when they are in a failed provisioning state.
Title: Message Title Azure DevOps started work on JENKINS-56824 Change By: Azure DevOps Status: Open In Progress 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.
[JIRA] (JENKINS-56824) VMs not cleaned up per retention policy when they are in a failed provisioning state.
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-56824 VMs not cleaned up per retention policy when they are in a failed provisioning state. Issue Type: Bug Assignee: Azure DevOps Attachments: windows-failed-azure.png, windows.failed.png Components: azure-vm-agents-plugin Created: 2019-03-31 19:21 Environment: Azure VM Agents 0.9.0, Jenkins 2.164.1 Priority: Minor Reporter: R. Tyler Croy This has happened a couple of times on ci.j.io. For whatever reason, we're not entirely sure, the init script for our Windows VMs sometimes fails. As a result, the agents are provisioned in Azure, but Jenkins fails to launch the JNLP agent on the machines. Unfortunately, Jenkins doesn't clean up these resources properly using our 20 minute idle retention policy. I discovered this morning that we had 50 VMs online for quite a few days, which never executed a single workload because their init script failed to run, and they were not cleaned up properly by the plugin.
