-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
Jenkins 2.303.3, Ec2 plugin 1.66
The Jenkins EC2 plugin isn't starting existing (stopped) nodes, instead, it always starts a new one. I can see the past instances as offline in the nodes tab, but instead of starting these nodes, the plugin always starts a new instance instead.
- relates to
-
JENKINS-64520 EC2 node not start after stop/disconnect with parameter Idle termination time
-
- Open
-
[JENKINS-67190] EC2-plugin not spooling up stopped nodes, starting new nodes instead
Priority | Original: Major [ 3 ] | New: Blocker [ 1 ] |
Assignee | Original: FABRIZIO MANFREDI [ thoulen ] |
I have set the instance cap to 1, and that just makes the queue stuck. It says the stopped instance is offline and won't try to connect to it. The same thing happens if I turn the instance on in AWS, I need to go on Jenkins and select "launch agent" for Jenkins to recognize the agent as online and the build to start.
The expected behavior should be that Jenkins starts the instance automatically and tries to reconnect to it