[
https://issues.apache.org/jira/browse/LIBCLOUD-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738274#comment-13738274
]
ASF subversion and git services commented on LIBCLOUD-363:
----------------------------------------------------------
Commit 73559d0b741e8f86dcb8c0075eac714c32466185 in branch refs/heads/trunk from
[~bobt]
[ https://git-wip-us.apache.org/repos/asf?p=libcloud.git;h=73559d0 ]
Issue LIBCLOUD-363: Fix ElasticHosts bug. Now checks for HTTP 204 and HTTP 200
to determine drive imaging status.
Signed-off-by: Tomaz Muraus <[email protected]>
> 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
> 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
