New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NoDelayProvisionStrategy won't provision after scaling down to 0 instances in auto scaling group #425
Comments
I was able to get it to work for a single run by setting "Minimum Spare Size" to 1, but then when I started another build after that, it hit the issue when provisioning the first node that time. It seems like, more generally, this is an issue with scaling out shortly after scaling in. |
We are also seeing this issue. When there are no agents available, meaning they are all scale down. The plugin won In the logs it says:
I'm wondering why it actually says that there is availableCapacity when clearly there is none and no scale up is triggered. |
@cccCody Did you manage to find the cause of this? |
I encountered a similar problem
Output
There were no jobs running |
I think we are running into the same issue here, with the NoDelayProvisioningStrategy. Digging around in the issues I found #149 - this one reads like a regression. Could that be? Restarting Jenkins "fixed" the issue, but I suspect it will come back. Then I will run the script console snippet of @snowman-papa to see if we also have "stuck planned" machines. |
I have faced the same issue on 3.2.0. Once we have switched to ASG from SpotFleet. My SpotFleet was setup with Min = 0 and Spare = 0 and after it scaled down to 0 instance. For 1.5h it didn't scale up while jobs were waiting in queue. I needed to increase min and spare in order it to work. |
We downgraded the plugin from 3.2.0 to 3.0.1. Waiting for a fix for this issue. |
I think this is the same issue as #180
Describe the bug
I'm currently trying to move from ec2-plugin to this plugin, but I'm seeing that the final stage of my build doesn't ever get an executor. My build looks roughly like this:
Everything works nicely until the last step, where it gets stuck on:
When I check the system logs, I see this on repeat:
I'm especially suspicious of
plannedCapacitySnapshot 1
, which, if I'm reading the source code right, seems to mean that it thinks it's already started scaling up another node (and is waiting for it to come online?) but it never does.Other misc info, may or may not be relevant:
Environment Details
Plugin Version?
3.1.0 (latest as of opening this)
Jenkins Version?
2.426.1 (latest LTS version as of opening this issue)
Spot Fleet or ASG?
ASG
Label based fleet?
no
Linux or Windows?
linux
The text was updated successfully, but these errors were encountered: