![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Francis Upton
|
|
Components:
|
ec2-plugin |
|
Created:
|
30/Nov/14 9:27 PM
|
|
Description:
|
I notice that the ec2 plugin fails to launch new ec2 instances/slave if the previous one had some errors.
I kicked off 100+ jobs all tied to the same ami and noticed that build queue did not move for hours. I could see that some of the nodes were in offline status with the following log
just before slave Ubuntu-UI-Slave (i-4a38xxx) gets launched ...
executing pre-launch scripts ...
Node Ubuntu-UI-Slave (i-4a38xxx)(i-4a38xxx) is still stopping, waiting 5s
Node Ubuntu-UI-Slave (i-4a38xxx)(i-4a38xxx) is still stopping, waiting 5s
Node Ubuntu-UI-Slave (i-4a38xxx)(i-4a38xxx) is terminated or terminating, aborting launch
These instances showed as 'terminated' on aws due to some error. The side effect was that jenkins was not able to provision any new slaves till the offline slaves were manually cleared/deleted.
The plugin should be able to delete such instances automatically.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Blocker]() Blocker
|
|
Reporter:
|
arazauci
|
|
|
|
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.
