-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins ver. 2.60.3; Amazon EC2 plugin: 1.36
After launching slave, I've got the following error:
This agent is offline because Jenkins failed to launch the agent process on it. See log for more details.
Here is the log:
ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins java.lang.NullPointerException at hudson.plugins.ec2.EC2SpotSlave.getSpotRequest(EC2SpotSlave.java:114) at hudson.plugins.ec2.EC2SpotSlave.getInstanceId(EC2SpotSlave.java:155) at hudson.plugins.ec2.EC2Computer.getInstanceId(EC2Computer.java:70) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:58) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:262) 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)
The slave nodes are running fine.
Affected code of line:
List<Reservation> reservations = getCloud().connect().describeInstances(request).getReservations();
The problem was a missing cloud settings which disappeared after some upgrades. Recovering previous data in clouds/hudson.plugins.ec2.EC2Cloud section in config.xml solved the problem.
But I think there should be some nicer way of informing the user about it.