Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
ec2-plugin 1.40.1
Description
Stopped ec2 instances are no longer being resumed when needed. Instead, new instances are spun up.
Instances were correctly resumed in version 1.39 but not in 1.40.1. Reverting to 1.39 fixed the issue for me.
This recent pull request appears to have removed the logic necessary to resume stopped instances.
https://github.com/jenkinsci/ec2-plugin/pull/252
Specifically the changes here:
https://github.com/jenkinsci/ec2-plugin/pull/252/files#diff-f2115e33148d3db7c133fe014ad9dfddR419
Attachments
Issue Links
- duplicates
-
JENKINS-53920 After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
-
- Resolved
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue duplicates |
Link |
This issue duplicates |
Attachment | ec2.log [ 45027 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Link |
This issue duplicates |
Resolution | Fixed [ 1 ] | |
Status | In Progress [ 3 ] | Closed [ 6 ] |
The PR-252 improved performance, it also fixed the problem of the doble connection to the node, unfortunately the automatically connection of the core is triggered only for new node and not for existing one.
The fix will be in the 1.41 (PR-311)
can you try the last snapshot of the 1.41 :
https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/ec2/1.41-SNAPSHOT/ec2-1.41-20181017.001057-2.hpi
don't forget to add the new permission to the Role:
{ "Sid": "VisualEditor1", "Effect": "Allow", "Action": [ "iam:ListInstanceProfilesForRole", "iam:PassRole" ], "Resource": "*" }