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

Posted to notifications@libcloud.apache.org by "Tomaz Muraus (JIRA)" <ji...@apache.org> on 2013/08/13 16:36:49 UTC

[jira] [Resolved] (LIBCLOUD-363) ElasticHosts: Checking wrong HTTP Response status code

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

Tomaz Muraus resolved LIBCLOUD-363.
-----------------------------------

    Resolution: Fixed
      Assignee: Tomaz Muraus

Sorry for the delay, I've totally missed out this issue.

I've merged the patch into trunk now - thanks!
                
> ElasticHosts:  Checking wrong HTTP Response status code
> -------------------------------------------------------
>
>                 Key: LIBCLOUD-363
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-363
>             Project: Libcloud
>          Issue Type: Bug
>            Reporter: Bob Thompson
>            Assignee: Tomaz Muraus
>            Priority: Trivial
>         Attachments: LIBCLOUD-363.patch
>
>
> In the ElasticHosts create_node() method, we are checking for the wrong response status to determine drive imaging success/failure. It should check HTTP 200 instead of 204.
> Modify ElasticStack to check for both.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira