-
Bug
-
Resolution: Fixed
-
Blocker
-
None
-
-
1.44.1
Tested with plugin version 1.38, Jenkins versions 2.73.3 and 2.89.1. All jobs are pipeline type jobs.
After upgrading from 1.36 to 1.38 (1.37 was not available), instances that are automatically spun up by jobs requesting to be run on a specific node label will have the instance launched in EC2, but the node never registers with Jenkins. Even the system logs, shown below, indicate that the plugin recognizes the new instance but it never registers as a node. The result is that jobs hang indefinitely with the message: Jenkins does have label insertlabelhere
I can manually launch instances from the Manage Nodes page and everything works as intended, but automatic provisioning exhibits the behavior described above.
Dec 08, 2017 11:03:38 AM hudson.plugins.ec2.EC2Cloud provision INFO: Attempting to provision slave from template hudson.plugins.ec2.SlaveTemplate@20e5213f needed by excess workload of 1 units of label 'ec2-docker-node6' Considering launching ami-111111 for template Docker-17.03.1-ce/Node6/NPM3.10/RHEL7 Dec 08, 2017 11:03:40 AM hudson.plugins.ec2.SlaveTemplate logProvisionInfo INFO: Considering launching ami-111111 for template Docker-17.03.1-ce/Node6/NPM3.10/RHEL7 Setting Instance Initiated Shutdown Behavior : ShutdownBehavior.Terminate Dec 08, 2017 11:03:40 AM hudson.plugins.ec2.SlaveTemplate logProvisionInfo INFO: Setting Instance Initiated Shutdown Behavior : ShutdownBehavior.Terminate Looking for existing instances with describe-instance: <instance details excluded to save space> checkInstance: <instance details excluded to save space> true - Instance has no node, but can be used Found existing instance: <instance details excluded to save space> Dec 08, 2017 11:03:41 AM hudson.plugins.ec2.SlaveTemplate logProvisionInfo INFO: Found existing pending or running: running instance: <instance details excluded to save space> Dec 08, 2017 11:03:41 AM hudson.plugins.ec2.EC2Cloud provision INFO: We have now 1 computers Dec 08, 2017 11:03:41 AM hudson.plugins.ec2.EC2Cloud provision INFO: Attempting provision - finished, excess workload: 0
[JENKINS-48459] Automatic provisioning launches instances, but fail to register them as nodes
Seeing the same issue on 1.38. Instantly spins up the maximum number of EC2 instances (8) but never registers them as nodes.
i can spin up slaves manually and they function, but i need to force remove slaves to free up instance capacity.
- changing the value of Instance Cap seemed to correct the issue
Simon Elliott
added a comment - - edited Seeing the same issue on 1.38. Instantly spins up the maximum number of EC2 instances (8) but never registers them as nodes.
i can spin up slaves manually and they function, but i need to force remove slaves to free up instance capacity.
changing the value of Instance Cap seemed to correct the issue
Klaus Schniedergers
added a comment - I have the same issue with ec2-plugin 1.38 an Jenkins 2.89.3.
The EC2 instance spins up, but never gets registered as node.
It works fine with ec2-plugin 1.36 and Jenkins 2.73.3 (Updating to 2.89.3 requires the EC2 update due to https://issues.jenkins-ci.org/browse/JENKINS-47593).
Klaus Schniedergers
added a comment - I have the same issue with ec2-plugin 1.38 an Jenkins 2.89.3.
The EC2 instance spins up, but never gets registered as node.
It works fine with ec2-plugin 1.36 and Jenkins 2.73.3 (Updating to 2.89.3 requires the EC2 update due to https://issues.jenkins-ci.org/browse/JENKINS-47593 ).
Klaus Schniedergers
added a comment - Following the tip in https://issues.jenkins-ci.org/browse/JENKINS-47130 fixed it (i.e. simply changing the instance type in the cloud setting which seems to regenerate config).
Klaus Schniedergers
added a comment - Following the tip in https://issues.jenkins-ci.org/browse/JENKINS-47130 fixed it (i.e. simply changing the instance type in the cloud setting which seems to regenerate config). 
FABRIZIO MANFREDI
added a comment - Most of the new features now have a default 
Seeing the same exact behavior with version 1.37. Will downgrade to v1.36 for now.