-
Bug
-
Resolution: Unresolved
-
Blocker
-
None
-
Jenkins v2.12 / Ubuntu 14.04.4 x86_64 / Oracle Java 1.80_91-b14
Hi,
We've recently started seeing a problem auto-launching EC2 build slaves. The plugin detects that it needs to launch a slave to meet demand and that no current instances are runnign - it just doesn't launch anything.
Manual provisioning works.
Log (some info sanitised):
Jul 08, 2016 3:47:34 PM hudson.plugins.ec2.EC2Cloud provision
INFO: Attempting to provision slave from template hudson.plugins.ec2.SlaveTemplate@6a756eca needed by excess workload of 1 units of label 'null'
Jul 08, 2016 3:47:34 PM hudson.plugins.ec2.EC2Cloud provision
WARNING: Label is null - can't calculate how many executors slave will have. Using 2 number of executors
Considering launching ami-6c14310f for template Remote Ubuntu 14.04 Docker Machine
Jul 08, 2016 3:47:34 PM hudson.plugins.ec2.SlaveTemplate logProvisionInfo
INFO: Considering launching ami-6c14310f for template Remote Ubuntu 14.04 Docker Machine
Setting Instance Initiated Shutdown Behavior : ShutdownBehavior.Terminate
Jul 08, 2016 3:47:34 PM hudson.plugins.ec2.SlaveTemplate logProvisionInfo
INFO: Setting Instance Initiated Shutdown Behavior : ShutdownBehavior.Terminate
Looking for existing instances with describe-instance: {InstanceIds: [],Filters: [{Name: image-id,Values: [ami-6c14310f]}, {Name: subnet-id,Values: [subnet-XXXXX]}, {Name: instance.group-id,Values: [sg-XXXXX]}, {Name: key-name,Values: [XXXXX]}, {Name: instance-type,Values: [t2.small]}, {Name: tag:Name,Values: [Jenkins Build Slave]}],}
No existing instance found - but cannot create new instance
Jul 08, 2016 3:47:34 PM hudson.plugins.ec2.EC2Cloud provision
INFO: Attempting provision - finished, excess workload: 1
