[JIRA] (JENKINS-40288) Generated storage account name is only using "resource group" for generation of GUID

2016-12-13 Thread clgui...@microsoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Claudiu Guiman closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40288  
 
 
  Generated storage account name is only using "resource group" for generation of GUID   
 

  
 
 
 
 

 
Change By: 
 Claudiu Guiman  
 
 
Status: 
 Open Closed  
 
 
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-40288) Generated storage account name is only using "resource group" for generation of GUID

2016-12-13 Thread scm_issue_l...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 SCM/JIRA link daemon commented on  JENKINS-40288  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Generated storage account name is only using "resource group" for generation of GUID   
 

  
 
 
 
 

 
 Code changed in jenkins User: Claudiu Guiman Path: src/main/java/com/microsoft/azure/AzureVMAgentTemplate.java http://jenkins-ci.org/commit/azure-vm-agents-plugin/2f144469b98b6bce9a083688ee9620dc352bd4ee Log: Generate the storage account name from subscription id and resource group name JENKINS-40288  
 

  
 
 
 
 

 
 
 

 
 
 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-40288) Generated storage account name is only using "resource group" for generation of GUID

2016-12-07 Thread clgui...@microsoft.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Claudiu Guiman commented on  JENKINS-40288  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Generated storage account name is only using "resource group" for generation of GUID   
 

  
 
 
 
 

 
 The fix is waiting for code review and testing: https://github.com/jenkinsci/azure-vm-agents-plugin/pull/3  
 

  
 
 
 
 

 
 
 

 
 
 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-40288) Generated storage account name is only using "resource group" for generation of GUID

2016-12-07 Thread ty...@monkeypox.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 R. Tyler Croy created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40288  
 
 
  Generated storage account name is only using "resource group" for generation of GUID   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Claudiu Guiman  
 
 
Components: 
 azure-vm-agents-plugin  
 
 
Created: 
 2016/Dec/07 7:22 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 R. Tyler Croy  
 

  
 
 
 
 

 
 I have two subscriptions for difference Jenkins masters, when I used the same "Resource Group" in the UI, the automatically generated "Storage Account Name" created the same name on both Jenkins masters leading to an ARM template deployment failure. I think the fix would be to use a hash of the Subscription ID and the Resource Group name to generate the storage acocunt name since that must be globally unique  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment