Repository navigation
fix(e2e): reclaim matching non-AB GPUs on quota failures - #10026
Draft
Ganeshkumar Ashokavardhanan (ganeshkumarashok) wants to merge 2 commits into
Draft
Ganeshkumar Ashokavardhanan (ganeshkumarashok) wants to merge 2 commits into
Ganeshkumar Ashokavardhanan (ganeshkumarashok) wants to merge 2 commits into
Conversation
Contributor
Windows Unit Test Results 3 files 21 suites 1m 5s ⏱️ Results for commit 82321cc. ♻️ This comment has been updated with latest results. |
Contributor
Contributor
Contributor
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Give AgentBaker GPU E2E VM creation priority over non-AgentBaker standalone GPU VMs and uniform scale sets in subscription
8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8.On a confirmed Compute core-quota error, use the final VMSS request model and Azure's GPU capability catalogue to find resources with the exact same VM size, region, and Spot/regular priority. Delete one eligible resource, wait for deletion to finish, pause 15 seconds for quota propagation, and retry creation. Recovery is bounded to three retries per scenario attempt, including outer provisioning retries and VHD-caching stages.
Destructive-operation boundary
buildIDandKEEP_VMSStags, AKS-managed resources, managed resource groups, flexible scale sets, and VMSS-member VMs.Verification follow-up
Adversarial tests reproduced and fixed four issues:
ResponseError.Error(): request URLs containingcoresmust not turn a VM-count quota into destructive core-quota recovery.Validation
cd e2e && go test ./... -race -count=1 -timeout 5mgo vet ./...,gofmt, andgit diff --check.The full E2E module race run passed 967 test/subtest records across eight tested packages, including 34 GPU-quota cases. Mocked Azure tests cover VM/VMSS reclamation, final-model SKU selection, async quota/deletion responses, protected resources, exact SKU/region/priority, pagination, changed resource metadata, shared retry limits, cleanup errors, cancellation, recovery contention, and SSH cleanup.
On the initial PR revision (
1e7090dc), hosted GPU E2E build190297396passed and its task log confirms one exact-SKU resource deletion completed after a core-quota failure. No manual Azure cleanup was executed. Linux E2E190297378failed containerd package validation, and Windows E2E190297388failed exporter/capacity checks; those are not quota-reclamation failures and remain outside this change. Hosted checks for this follow-up revision must finish before claiming that revision is green.