[jira] [Commented] (JCLOUDS-972) Failed EC2 spot instance requests through compute service never return correctly

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

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

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

Commit 6c94f3eb9ec82cda40ee8b1718594789e99805d0 in jclouds's branch refs/heads/1.9.x from [~abayer]
[ https://git-wip-us.apache.org/repos/asf?p=jclouds.git;h=6c94f3e ]

JCLOUDS-972. Fix parsing of spot reqs, set sane default for validUntil.

Get the faultCode and faultMessage to actually be parsed (though I'm
not sure they're ever used), add statusCode, statusMessage and
statusUpdateTime, and have AWSEC2TemplateOptions default to a sane 30
minute lifetime for spot instance requests, so they don't get orphaned
forever if the price is too low etc.


> Failed EC2 spot instance requests through compute service never return correctly
> --------------------------------------------------------------------------------
>
>                 Key: JCLOUDS-972
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-972
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-compute
>    Affects Versions: 1.9.0
>            Reporter: Andrew Bayer
>            Assignee: Andrew Bayer
>             Fix For: 2.0.0, 1.9.1
>
>
> If a spot instance request, created through the compute service, has too low a price or insufficient capacity, etc, the spot instance request will get a fault code and fault message added, but will never actually switch out of the "open" state. As a result, the block-until-running logic just keeps going, since the spot-to-instance converter always returns a PENDING state.



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