-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
Jenkins ver. 2.7.1
Amazon EC2 Plugin ver. 1.35
If multiple Eucalyptus clouds are defined in the plugin, the following error shows when the EC2 build image is launched:
ERROR: The instance ID 'i-85a826d1' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidInstanceID.NotFound; Request ID: c0492dd8-2548-4637-9a03-161c37654b72) com.amazonaws.AmazonServiceException: The instance ID 'i-85a826d1' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidInstanceID.NotFound; Request ID: c0492dd8-2548-4637-9a03-161c37654b72) at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1307) at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:894) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:597) at com.amazonaws.http.AmazonHttpClient.doExecute(AmazonHttpClient.java:363) at com.amazonaws.http.AmazonHttpClient.executeWithTimer(AmazonHttpClient.java:329) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:308) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:13032) at com.amazonaws.services.ec2.AmazonEC2Client.describeInstances(AmazonEC2Client.java:9037) at hudson.plugins.ec2.EC2Computer._describeInstanceOnce(EC2Computer.java:166) at hudson.plugins.ec2.EC2Computer._describeInstance(EC2Computer.java:160) at hudson.plugins.ec2.EC2Computer.getState(EC2Computer.java:125) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:80) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:253) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)
Logging into Eucalyptus shows in fact that the instance has launched correctly with all the correct settings (keys, security groups, etc.) as defined in the cloud configuration.
It appears as though it is searching the first cloud for the instance, when it was launched in the second, similar to the issue in JENKINS-12547, which resolved the issue for Amazon EC2 (but it appears not Eucalyptus)
Also of note, when you attempt to launch the node manually using the Provision via eucalyptus option, you get the following:
java.lang.Exception: No such template: TEMPLATE_NAME
This has been reported in and appears related to JENKINS-24663