lock step fails right away if it
requests a label quantity bigger than the number of resources with that
label, including extra entries. Such a request could otherwise never be
satisfied with the current set of resources.
When disabled, the step waits until enough resources with that label exist. This is
useful when resources appear later, for example cloud nodes that are provisioned
after the build starts.