![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Francis Upton
|
|
Components:
|
ec2-plugin |
|
Created:
|
19/Nov/14 3:22 PM
|
|
Description:
|
We have quite a few ec2 slave configurations. Recently we've added a configuration which uses spot instances.
When a job is run which triggers the request to launch the spot instance, and so long as the instance is not launched or deleted, other jobs triggering the launch of the non-spot instances will hang forever and their instances will not be attempted to be launched.
As soon as I delete the spot instance (which is in the down state since it hasn't called back yet), the non-spot instance is provisioned and and the hung job is executed.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Timor Raiman
|
|
|
|
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
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
