[
https://issues.apache.org/jira/browse/WHIRR-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149738#comment-13149738
]
Andrei Savu commented on WHIRR-431:
-----------------------------------
Created a jclouds issue for this
http://code.google.com/p/jclouds/issues/detail?id=751 - looking for a fix now.
It seems like the problem is real because the live test [1] does explicit
cancelation before terminating the instances.
[1]
https://github.com/jclouds/jclouds/blob/master/providers/aws-ec2/src/test/java/org/jclouds/aws/ec2/services/SpotInstanceClientLiveTest.java
> Spot instance requests are not cancelled after cluster "destruction"
> --------------------------------------------------------------------
>
> Key: WHIRR-431
> URL: https://issues.apache.org/jira/browse/WHIRR-431
> Project: Whirr
> Issue Type: Bug
> Reporter: Marco Didonna
> Labels: ec2
>
> I've noticed that when using spot instances, first a request is created and,
> when fulfilled, the associated instances are launched. Standard operating
> procedure on EC2. The problem is when the cluster is destroyed the spot
> request are still there (in an open state) and new instances may be assigned
> to them. I've experienced this behavior three times before starting to
> manually delete spot request when the cluster is no longer needed.
> Anyone can confirm?
--
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
