-
Bug
-
Resolution: Unresolved
-
Major
-
Jenkins LTS 1.642.1
ec2-1.31
Hi since 1.31 we have had issues of spot slaves being unable to be created due to it exceeding the cap.
Our setup is:
Base AMI for our build process
Multiple VPC to our different environments
Cap on each AMI in different VPC
The cap count seems to be for all AMI, not AMI per config, so we could have spot in 4 VPC but can't launch one in the 5th VPC.
This is for automatic launch and for manual launching of the spot instance in the 5th VPC.
Docs say: "Limit the total number of running instances launched from this AMI and associated configurations."
This does not seem to be the case with 1.31, seems to just be "Limit the total number of running instances launched from this AMI"
Also seeing this since 1.31
2 ec2 configs in the same cloud sharing the same AMI. First config with limit 4. Second config with limit 2.
2 instances of config 1 are launched -> cannot launch any of config 2
Change instance limit of config 2 to 3+ -> config 2 launches
My guess is that the limits are read per config but the total when launching an instance from a config is calculated from all instances using that AMI.
Note: If it makes any difference, the instances above were all spot instances.