hudson.slaves.NodeProvisioner - wrong computer(s) count

[Torsten Krah]

Hi,

running jenkins 2.401.1 I've got a problem with the node provisioning.

E.g.:

Jun 07, 2023 10:00:00 AM hudson.triggers.SCMTrigger$Runner run
INFO: SCM changes detected in Bitbucket Development Branch. Triggering #3
Jun 07, 2023 10:00:12 AM hudson.slaves.NodeProvisioner update
INFO: abc-node-ctp6c provisioning successfully completed. We have now 6 computer(s)

it is telling me that there are now 6 computer(s), but there are only 4
nodes spawned and it won't spawn 5+6 now.
Lowering the maximum nodes e.g. to 4 does result in the same wrong
behavior that it is e.g. writing is has 4 computers, but only 2 are
spawned, or having 25 in the log message and only 15 nodes are there in
reality.
Something is odd about that counter.

Does anyone have an idea if that is a bug or how to force jenkins to
recount the spawned nodes to force the provisioner to spawn new nodes
until the maximum configured if there are entries waiting in the queue?

kind regards

Torsten

--