-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
Jenkins 2.8
EC2-Plugin 1.33
This happens when I start new job and the plugin try to create new slave. However the slaves never get online instead the plugin try to create new slave over and over. I have tried to set Launch Timeout in seconds to 0 (infinite) but it doesn't works.
Jun 10, 2016 9:13:37 AM null
FINEST: Node (i-5727dc86)(i-5727dc86) is still pending/launching, waiting 5s
Jun 10, 2016 9:13:42 AM null
FINEST: Node (i-5727dc86)(i-5727dc86) is still pending/launching, waiting 5s
Jun 10, 2016 9:13:47 AM null
FINEST: Node (i-5727dc86)(i-5727dc86) is still pending/launching, waiting 5s
Jun 10, 2016 9:13:52 AM null
FINEST: Node (i-5727dc86)(i-5727dc86) is still pending/launching, waiting 5s
Jun 10, 2016 9:13:57 AM null
FINEST: Node (i-5727dc86)(i-5727dc86) is still pending/launching, waiting 5s
Jun 10, 2016 9:14:02 AM null
FINEST: Node (i-5727dc86)(i-5727dc86) is still pending/launching, waiting 5s
Jun 10, 2016 9:14:07 AM null
FINEST: Node (i-5727dc86)(i-5727dc86) is still pending/launching, waiting 5s
Jun 10, 2016 9:14:12 AM null
FINEST: Node (i-5727dc86)(i-5727dc86) is still pending/launching, waiting 5s
Jun 10, 2016 9:14:17 AM null
FINEST: Node (i-5727dc86)(i-5727dc86) is still pending/launching, waiting 5s
Jun 10, 2016 9:14:23 AM null
FINEST: Node (i-5727dc86)(i-5727dc86) is still pending/launching, waiting 5s
Jun 10, 2016 9:14:28 AM null
FINEST: Node (i-5727dc86)(i-5727dc86) is still pending/launching, waiting 5s
Jun 10, 2016 9:14:33 AM null
INFO: Node (i-5727dc86)(i-5727dc86) is terminated or terminating, aborting launch
[JENKINS-35524] new ec2 slave is terminated or terminating during launch
Summary | Original: new ec2 slave is terminated/terminating during launch | New: new ec2 slave is terminated or terminating during launch |
Workflow | Original: JNJira [ 171834 ] | New: JNJira + In-Review [ 184496 ] |
This is hitting us really big, at the moment we have over 400 ec2 instances that were started and terminated instantly. Using Jenkins 2.19.4 and ec2-plugin 1.36.
Agent logs show only this:
INFO: Node ***** (i-0045d9d744706f494)(i-0045d9d744706f494) is terminated or terminating, aborting launch