![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Francis Upton
|
|
Components:
|
ec2 |
|
Created:
|
08/Dec/12 12:04 PM
|
|
Description:
|
When using the EC2 plugin with EBS-based hosts and an idle timeout after which the instances are stopped, the EC2 plugin treats a manually started host as if it were dead if Jenkins expected it to be stopped.
As far as I can tell, if the EC2 plugin's EC2 API call to start the stopped host fails (say, because the host has already been started so an admin can investigate the working tree of a failed build in-situ) it assumes the host is dead. It should instead query the host's state to determine if it's running and if it is, proceed with starting the agent as if it'd successfully started it its self.
I'm not asking anybody to make this change for me; this report is here to explain the issue to others who encounter it and as a note to remind me of what I need to do if I get time to address this issue.
|
|
Environment:
|
Host is Debian 6 with OpenJDK 6 but issue appears host-independent
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Craig Ringer
|
|
|
|
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
|
