From 018838ec7beeb6b446e6ad1be8c7eb1fc1a715fe Mon Sep 17 00:00:00 2001 From: Ganeshkumar Ashokavardhanan Date: Wed, 22 Apr 2026 10:24:06 -0700 Subject: [PATCH] fix(e2e): drop hardcoded D2s_v3 system pool from MA35D scenarios Both Test_AzureLinuxV3_MA35D and Test_AzureLinuxV3_MA35D_Scriptless pinned the AKS system node pool to Standard_D2s_v3 in eastus. That SKU is currently subscription-restricted across all eastus availability zones ("All availability zones are restricted for this SKU"), so cluster creation fails with 400 BadRequest before the scenario can exercise the MA35D GPU node under test. Removing the override falls back to config.DefaultVMSKU (Standard_D2ds_v5), which every other GPU/non-GPU scenario already uses successfully for the system pool. The MA35D GPU SKU itself (Standard_NM16ads_MA35D) is unchanged. Observed in build 161380177 on PR #8228: RESPONSE 400: 400 Bad Request The VM size of 'Standard_D2s_v3' is currently not available in your subscription in location 'eastus'. --- e2e/scenario_test.go | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/e2e/scenario_test.go b/e2e/scenario_test.go index cf9ba4e426e..cc1d9a4f07a 100644 --- a/e2e/scenario_test.go +++ b/e2e/scenario_test.go @@ -1824,8 +1824,7 @@ func Test_AzureLinuxV3_MA35D(t *testing.T) { }, }, // No MA35D GPU capacity in West US, so using East US - Location: "eastus", - K8sSystemPoolSKU: "Standard_D2s_v3", + Location: "eastus", }) } @@ -1854,8 +1853,7 @@ func Test_AzureLinuxV3_MA35D_Scriptless(t *testing.T) { }, }, // No MA35D GPU capacity in West US, so using East US - Location: "eastus", - K8sSystemPoolSKU: "Standard_D2s_v3", + Location: "eastus", }) }