[JIRA] (JENKINS-41330) Extra VMs left running in Resource Group

2017-02-16 Thread clgui...@microsoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Claudiu Guiman closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41330  
 
 
  Extra VMs left running in Resource Group   
 

  
 
 
 
 

 
Change By: 
 Claudiu Guiman  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 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.


[JIRA] (JENKINS-41330) Extra VMs left running in Resource Group

2017-02-07 Thread clgui...@microsoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Claudiu Guiman edited a comment on  JENKINS-41330  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Extra VMs left running in Resource Group   
 

  
 
 
 
 

 
 The fix will make sure there are no leaked deployments provisioned with Azure VM Agents 0.4.2+After you upgrade to the latest plugin (there's probably going to be a release next week) please make sure you don't have any older leaked resources  (new resource will have this tag key/value: JenkinsManagedTag:ManagedByAzureVMAgents) .   
 

  
 
 
 
 

 
 
 

 
 
 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.


[JIRA] (JENKINS-41330) Extra VMs left running in Resource Group

2017-02-07 Thread clgui...@microsoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Claudiu Guiman commented on  JENKINS-41330  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Extra VMs left running in Resource Group   
 

  
 
 
 
 

 
 The fix will make sure there are no leaked deployments provisioned with Azure VM Agents 0.4.2+ After you upgrade to the latest plugin (there's probably going to be a release next week) please make sure you don't have any older leaked resources.  
 

  
 
 
 
 

 
 
 

 
 
 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.


[JIRA] (JENKINS-41330) Extra VMs left running in Resource Group

2017-02-07 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41330  
 
 
  Extra VMs left running in Resource Group   
 

  
 
 
 
 

 
Change By: 
 SCM/JIRA link daemon  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 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.


[JIRA] (JENKINS-41330) Extra VMs left running in Resource Group

2017-01-27 Thread clgui...@microsoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Claudiu Guiman started work on  JENKINS-41330  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Claudiu Guiman  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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.


[JIRA] (JENKINS-41330) Extra VMs left running in Resource Group

2017-01-26 Thread clgui...@microsoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Claudiu Guiman commented on  JENKINS-41330  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Extra VMs left running in Resource Group   
 

  
 
 
 
 

 
 I'll update the cleanup task to remove all resources from the resource group, not just the one that got deleted.  
 

  
 
 
 
 

 
 
 

 
 
 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.


[JIRA] (JENKINS-41330) Extra VMs left running in Resource Group

2017-01-23 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41330  
 
 
  Extra VMs left running in Resource Group   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Claudiu Guiman  
 
 
Attachments: 
 Selection_048.png, Selection_049.png, Selection_050.png  
 
 
Components: 
 azure-vm-agents-plugin  
 
 
Created: 
 2017/Jan/23 4:23 PM  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 R. Tyler Croy  
 

  
 
 
 
 

 
 We had some templates fail to deploy on ci.jenkins.io, upon further investigation I discovered that the reason the ARM deploy had failed is because the resource group was exceeding a quota. It turns out, Azure has a *lot* more VMs spun up than our Jenkins currently has attached as agents. There are *six* VMs running in Azure and basically none are registered as agents in Jenkins. I don't know how long they all have been running Not sure what diagnostics could help, i'm going to delete these excess VMs so I can stop burning money.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment