[jira] [Commented] (JCLOUDS-946) The ImageExtension in DigitalOcean only works with the first available location

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCLOUDS-946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14624037#comment-14624037 ] 

ASF subversion and git services commented on JCLOUDS-946:
---------------------------------------------------------

Commit d246bc22eb277b0d1373078056ec3d7425786f80 in jclouds-labs's branch refs/heads/1.9.x from [~nacx]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds-labs.git;h=d246bc2 ]

JCLOUDS-946: Properly scope images to the locations where they are available


> The ImageExtension in DigitalOcean only works with the first available location
> -------------------------------------------------------------------------------
>
>                 Key: JCLOUDS-946
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-946
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-labs
>    Affects Versions: 1.9.0
>            Reporter: Ignasi Barrera
>            Assignee: Ignasi Barrera
>              Labels: digitalocean
>             Fix For: 2.0.0
>
>
> In DigitalOcean, in the ImageToImage function, the location is not being set. That means images are available in all regions. This assumption is not true, as the images created by the image extension (from a Droplet) are only available in the region of the source droplet.
> This is causing the image extension live test to fail in all regions but NYC1. The resulting image is missing the location id, and the template builder tries to find it in the default location (NYC1).
> This should be done in the V2 provider. All images have the list of regions where they are available, and jclouds should properly handle that to properly set the location field.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)