Skip to content
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

PreStage incorrectly reports batch node readiness if quota has been reached #513

Closed
jormdav opened this issue May 16, 2024 · 0 comments · Fixed by #514
Closed

PreStage incorrectly reports batch node readiness if quota has been reached #513

jormdav opened this issue May 16, 2024 · 0 comments · Fixed by #514

Comments

@jormdav
Copy link
Contributor

jormdav commented May 16, 2024

We'd a situation in our batch account where we attempted to provision more nodes than our 500 vCPU quota allowed:

image

However, when prestage was waiting for all of them to idle, it incorrectly reported that all 350 nodes were ready, when only 349 of them were.

image

image

The above example was created for illustrative purposes, where it bit us was a separate pool of 1 node that couldn't be created, but passed its prestage logic and moved onto enqueue/run, whereupon the batch job eventually timed out:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant