![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Francis Upton
|
|
Components:
|
ec2 |
|
Created:
|
29/Jul/13 11:11 PM
|
|
Description:
|
When the EC2 plugin is automatically allocating instances, an instance sometimes fails to start (ending up with a yellow dot on the EC2 control panel and 1/2 checks performed). When this happens, the jenkins slave loops through "waiting for SSH to come up" indefinitely.
Eventually, other instances will expire due to inactivity and we enter a state where only the looping instance exists. At this point, the system will not allocate any new instances and jobs will continually pile up until the looping instance is manually terminated. Once it is, jobs will resume normally.
|
|
Environment:
|
Jenkins is version 1.509.1 with EC2 plugin version 1.18 running on Ubuntu 8.04 and the EC2 instances are m2.4xlarge on Ubuntu
|
|
Project:
|
Jenkins
|
|
Labels:
|
plugin
slave
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Robin Keller
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
