[JIRA] [ec2-plugin] (JENKINS-33945) can't provision new nodes when a matching node is marked offline

[tba...@circle.com (JIRA)]

Title: Message Title

Trevor Baker commented on JENKINS-33945   Re: can't provision new nodes when a matching node is marked offline It is also a problem for nodes provisioned automatically via StandardStrategyImpl Create a 3x3 axis Multi-configuration job. Launch a single slave with the label that can run the job, then mark if offline. It won't start any new nodes and the job will be stuck. Mar 31, 2016 6:46:45 PM FINER hudson.slaves.NodeProvisioner Consulting hudson.slaves.NodeProvisioner$StandardStrategyImpl@6437ee5a provisioning strategy with state StrategyState{label=deployer, snapshot=LoadStatisticsSnapshot{definedExecutors=1, _onlineExecutors_=0, connectingExecutors=0, busyExecutors=0, idleExecutors=0, availableExecutors=0, queueLength=9}, plannedCapacitySnapshot=0, additionalPlannedCapacity=0} Mar 31, 2016 6:46:45 PM FINE hudson.slaves.NodeProvisioner Excess workload 7.906 detected. (planned capacity=0,connecting capacity=0,Qlen=7.906,available=0.174&0,_online_=0,m=0.5) Mar 31, 2016 6:46:45 PM FINE hudson.plugins.ec2.EC2Cloud Attempting provision, excess workload: 8 Mar 31, 2016 6:46:45 PM FINE hudson.plugins.ec2.EC2Cloud Counting current slaves: All AMIS Mar 31, 2016 6:46:45 PM FINE hudson.plugins.ec2.EC2Cloud Existing instance found: i-3a616ebe AMI: ami-ce2d26a4 Template: null Mar 31, 2016 6:46:45 PM FINE hudson.plugins.ec2.EC2Cloud Counting current slaves: AMI: ami-ce2d26a4 Mar 31, 2016 6:46:45 PM FINE hudson.plugins.ec2.EC2Cloud Existing instance found: i-3a616ebe AMI: ami-ce2d26a4 Template: Jenkins - Deployer Slave Mar 31, 2016 6:46:45 PM FINE hudson.plugins.ec2.EC2Cloud Available Total Slaves: 2147483646 Available AMI slaves: 2147483646 AMI: ami-ce2d26a4 TemplateDesc: Jenkins - Deployer Slave Mar 31, 2016 6:46:45 PM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo Launching ami-ce2d26a4 for template Jenkins - Deployer Slave Mar 31, 2016 6:46:46 PM FINE hudson.plugins.ec2.SlaveTemplate Looking for existing instances with describe-instance: {InstanceIds: [],Filters: [{Name: image-id,Values: [ami-ce2d26a4]}, {Name: availability-zone,Values: [us-east-1a]}, {Name: subnet-id,Values: [subnet-xxx]}, {Name: instance.group-id,Values: [sg-xxx]}, {Name: key-name,Values: [dev]}, {Name: instance-type,Values: [t2.small]}, {Name: tag:Name,Values: [DEV-JENKINSSLAVE]}, {Name: tag:ENV,Values: [DEV]}],} Mar 31, 2016 6:46:46 PM FINE hudson.plugins.ec2.SlaveTemplate checkInstance: {InstanceId: i-3a616ebe,ImageId: snip} Mar 31, 2016 6:46:46 PM FINE hudson.plugins.ec2.SlaveTemplate Found existing corresponding Jenkins slave: i-3a616ebe Mar 31, 2016 6:46:46 PM FINE hudson.plugins.ec2.SlaveTemplate true - Node has capacity - can use it Mar 31, 2016 6:46:46 PM FINE hudson.plugins.ec2.SlaveTemplate Found existing instance: {InstanceId: i-3a616ebe,snip} node: i-3a616ebe Mar 31, 2016 6:46:46 PM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo Found existing pending or running: running instance: {InstanceId: i-3a616ebe,snip} Mar 31, 2016 6:46:46 PM INFO hudson.plugins.ec2.SlaveTemplate logProvisionInfo Using existing slave: i-3a616ebe Instance i-3a616ebe in the above example is the temporarily offline node. Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.