![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Francis Upton
|
|
Attachments:
|
ec2_plugin.png |
|
Components:
|
ec2 |
|
Created:
|
31/Dec/13 2:18 PM
|
|
Description:
|
I want to use the "Amazon EC2 Plugin" to dynamically start slaves on EC2.
Versions:
Jenkins 1.544
Amazon EC2 Plugin 1.20
I am using the eu-west-1 region.
So far Jenkins starts the EC2 instance fine but Jenkins can not ssh into the slave. The plugin log looks like the following.
Connecting to 172.31.x.y on port 22.
Waiting for SSH to come up. Sleeping 5.
Connecting to 172.31.x.y on port 22.
Waiting for SSH to come up. Sleeping 5.
...
I already verified that:
- I can manually ssh into the instance created by jenkins using the credentials used by Jenkins (tested from the jenkins host)
- I can scp files into /tmp and /var/jenkins
- auth.log on the instance contains no login attempts
- adding the running instance as a static slave node works with same credentials
Therefore I am pretty convinced that it is a defect in Jenkins / the plugin.
The attached screenshot shows my plugin config in Jenkins.
I am happy to help analyzing this issue / retesting a fix.
|
|
Environment:
|
Ubuntu, EC2
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Mark Fink
|
|
|
|
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/groups/opt_out.
