[
https://issues.apache.org/jira/browse/JCLOUDS-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15823822#comment-15823822
]
Ignasi Barrera commented on JCLOUDS-1226:
-----------------------------------------
In order to fix this we should change the IDs of the hardware profiles to
include the id of the region as a prefix, just like we do in AWS or OpenStack
(region/id).
> Jclouds-labs: Region required in Azure ARM
> ------------------------------------------
>
> Key: JCLOUDS-1226
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1226
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-labs
> Affects Versions: 2.0.0
> Reporter: Duncan Godwin
> Labels: azurecompute-arm
>
> When launching a VM with the
> [Azurecompute-arm|https://github.com/jclouds/jclouds-labs/tree/e1670f5c97442be977bf97cbf3b35423b1377532/azurecompute-arm]
> module, if no region is specified the provisioning fails.
> Jclouds attempts to list the hardware profiles
> [here|https://github.com/jclouds/jclouds-labs/blob/2e3874301895557c366bc0c613605d68704f9305/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/compute/functions/VirtualMachineToNodeMetadata.java#L292-L297].
> This then calls the code
> [here|https://github.com/jclouds/jclouds-labs/blob/e1670f5c97442be977bf97cbf3b35423b1377532/azurecompute-arm/src/main/java/org/jclouds/azurecompute/arm/compute/AzureComputeServiceAdapter.java#L173-L186]
> which, if no region is specified, requests hardware profiles from all
> regions. Unfortunately the IDs returned are the same from all regions,
> leading to conflicting objects in the Map.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
