Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
None
Description
If multiple EC2 clouds are defined in the plugin, incorrect credentials seem to be used to issue commands for nodes in the second defined cloud. Instances for the second cloud can be created, but the Jenkins agent fails to connect, which results in a new node being created for each failed attempt. Once created, the nodes cannot be deleted until the first cloud is deleted.
Attachments
Activity
Francis Upton
added a comment - There remain problems with multiple cloud support that will be shortly addressed.
Francis Upton
added a comment - There remain problems with multiple cloud support that will be shortly addressed. Francis Upton
added a comment - Just checked in fixes that should make this work properly. I tested it with multiple clouds and both spot and demand instances. Also clarified that the cloud has to be uniquely identified by the region (and made the UI such that it would not allow duplicate EC2 clouds to be created).
Francis Upton
added a comment - Just checked in fixes that should make this work properly. I tested it with multiple clouds and both spot and demand instances. Also clarified that the cloud has to be uniquely identified by the region (and made the UI such that it would not allow duplicate EC2 clouds to be created). Francis Upton
added a comment - Here is the commit that had the remaining fixes. Note the bug report number in the commit message is incorrect:
https://github.com/jenkinsci/ec2-plugin/commit/9095d318589809ea69cd7e1ca9e1ff94012794d6
Francis Upton
added a comment - Here is the commit that had the remaining fixes. Note the bug report number in the commit message is incorrect:
https://github.com/jenkinsci/ec2-plugin/commit/9095d318589809ea69cd7e1ca9e1ff94012794d6 
Murali Phani
added a comment - Hi,
I am facing similar issue with EC2 1.29 as well.When two clouds are configured in EC2,the second one taking the first key to connect and failing..Please help which version has fix for this issue
Murali Phani
added a comment - Hi,
I am facing similar issue with EC2 1.29 as well.When two clouds are configured in EC2,the second one taking the first key to connect and failing..Please help which version has fix for this issue 
Code changed in jenkins
User: Francis Upton
Path:
src/main/java/hudson/plugins/ec2/EC2AbstractSlave.java
src/main/java/hudson/plugins/ec2/EC2Computer.java
src/main/java/hudson/plugins/ec2/EC2ComputerLauncher.java
src/main/java/hudson/plugins/ec2/EC2OndemandSlave.java
src/main/java/hudson/plugins/ec2/EC2SpotSlave.java
src/main/java/hudson/plugins/ec2/SlaveTemplate.java
src/main/java/hudson/plugins/ec2/ssh/EC2UnixLauncher.java
http://jenkins-ci.org/commit/ec2-plugin/5da8f6be66e839e33923cbf5e8b62b0f6c4b7bfc
Log:
Merge pull request #48 from rsennewald/jenkins-15081
Fix to allow multiple EC2Clouds (fix for
JENKINS-15081)Compare: https://github.com/jenkinsci/ec2-plugin/compare/881b2b80e488...5da8f6be66e8