Waiting for next available executor on ‘test i-123456789

[ajax-koval-i]

Issue Details

Short Description of the bug

I have for example 3 pipelines in jenkins with agent label exception {'ec2-fleet'}.
Settings of my cloud:

1. Max Idle Minutes Before Scaledown = 15
2. Minimum Cluster Size = 1
3. Maximum Cluster Size = 10
4. Maximum Total Uses = 1 (1 build on node)
5. Minimum Spare Size = 0

I have PRs for example with names:

1. test_1
2. test_2
3. test_3

I started my test_1 PR - he will start on ready node for example instance1 and build run very quickly after start.
After starting first PR, i starting test_2 and test_3 PRs. And I see this log output from these(test_2 and test_3) pipelines:

Waiting for next available executor on ‘test instance1

Then, when my test_1 PR was successfully done - my test_2 PR start on new instance - instance2, because instance1 has maximum total uses 1 and instance1 will imediatly shutdown.

Conclusion:
if you start for example in one time 3 pipelines with my configuration. Plugin will wait when first PR will ended, after that plugin will provision new instance for second PR, and when second PR will ended - plugin starts 3 pipeline.
queue time 10 minutes on the last pr - it is very big amount of time.

can you fix this?

Environment Details

Plugin Version?
3.2.0

Jenkins Version?
<2.434>

Spot Fleet or ASG?
ASG

Label based fleet?
No

Linux or Windows?
Linux

[icep87]

Do you have NoDelayProvisionStrategy enabled?

[ajax-koval-i]

@icep87 yeap

[An4ik]

i everyone, facing the same issue. but on ubuntu

Jenkins version: 2.414.3

[An4ik]

it's been fixed and working now for me.

I've just unchecked Restrict Usage (Only build jobs with label expressions matching this node).
Actually it was checked on testing purposes before.

on my build pipelines i also had set label ec2-fleet, so they were waiting for that worker.

cc: @ajax-koval-i

so i think it's because of

I have for example 3 pipelines in jenkins with agent label exception {'ec2-fleet'}.

i believe removing label will help,

but yeah, from my point of view it's a bug, since unexpected.
also it seemed it's related to jenkins itself.