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

Fixed the issue where the system would become unusable if Batch account contained a pool of VM size that is not on the supported list #472

Merged
merged 1 commit into from
Sep 8, 2022

Conversation

tonybendis
Copy link
Contributor

Fixed the issue where the system would become unusable if Batch account contained a pool of VM size that is not on the supported list.

Fixed the logic that determines the number of dedicated cores in use by VM family. Previously the logic considered just the requested VM size and not the entire family.

Fixes #421

…nt contained a pool of VM size that is not on the supported list. Fixed the logic that determines the number of dedicated cores in use by VM family.
@tonybendis tonybendis added this to the 3.2 milestone Sep 3, 2022
@tonybendis tonybendis merged commit 4187250 into develop Sep 8, 2022
@tonybendis tonybendis deleted the abendis/IgnoreUnknownVmSizes branch September 8, 2022 17:57
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 this pull request may close these issues.

Workflow fails if there is an existing Batch pool using unsupported VM size
2 participants