You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ace.apache.org by "Paul Bakker (Updated) (JIRA)" <ji...@apache.org> on 2011/10/18 23:57:11 UTC

[jira] [Updated] (ACE-187) AMIs can't be found because the search location is incorrect

     [ https://issues.apache.org/jira/browse/ACE-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Bakker updated ACE-187:
----------------------------

    Attachment: jclouds.patch
    
> AMIs can't be found because the search location is incorrect
> ------------------------------------------------------------
>
>                 Key: ACE-187
>                 URL: https://issues.apache.org/jira/browse/ACE-187
>             Project: Ace
>          Issue Type: Bug
>            Reporter: Paul Bakker
>         Attachments: jclouds.patch
>
>
> While using the Amazon node launcher AMIs that do exist can't be found by Ace. This is because jclouds now searches AMIs that already exist in the list of instances instead of in the general AMI directory. I fixed this by upgrading jclouds to 1.1.1 (it was still on an early beta) and by removing an deprecated and obsolete property where the ComputeServiceContextFactory is created.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira