Skip to content

chore(deps): update aks/aks-gpu-cuda docker tag to v595

fcf7a49
Select commit
Loading
Failed to load commit list.
Open

chore(deps): update aks/aks-gpu-cuda docker tag to v595 #8439

chore(deps): update aks/aks-gpu-cuda docker tag to v595
fcf7a49
Select commit
Loading
Failed to load commit list.
Azure Pipelines / AKS Windows VHD Build - PR check-in gate failed May 20, 2026 in 1h 37m 3s

Build #PR_20260520.4_merge_164853357 had test failures

Details

Tests

  • Failed: 2 (0.40%)
  • Passed: 502 (99.60%)
  • Other: 0 (0.00%)
  • Total: 504

Annotations

Check failure on line 1505 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / AKS Windows VHD Build - PR check-in gate

Build log #L1505

Script failed with exit code: 1

Check failure on line 1 in Test_Windows2025Gen2_WindowsCiliumNetworking/default

See this annotation in the file changed.

@azure-pipelines azure-pipelines / AKS Windows VHD Build - PR check-in gate

Test_Windows2025Gen2_WindowsCiliumNetworking/default

Failed
Raw output
=== RUN   Test_Windows2025Gen2_WindowsCiliumNetworking/default
=== PAUSE Test_Windows2025Gen2_WindowsCiliumNetworking/default
=== CONT  Test_Windows2025Gen2_WindowsCiliumNetworking/default
    test_helpers.go:390: [546.141s] TAGS {Name:Test_Windows2025Gen2_WindowsCiliumNetworking/default ImageName:windows-2025-gen2 OS:windows Arch:amd64 NetworkIsolated:false NonAnonymousACR:false GPU:false WASM:false BootstrapTokenFallback:false KubeletCustomConfig:false Scriptless:false VHDCaching:false MockAzureChinaCloud:false VMSeriesCoverageTest:false}
    test_helpers.go:221: [551.105s] β†’ running scenario...
    test_helpers.go:258: [560.697s] β†’ preparing AKS node...
    vmss.go:476: [572.331s] β†’ creating VMSS winen15...
    vmss.go:384: [572.340s] VMSS portal link: https://ms.portal.azure.com/#@microsoft.onmicrosoft.com/resource/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/MC_abe2e-westus3_abe2e-azure-network-v3-f69fa_westus3/providers/Microsoft.Compute/virtualMachineScaleSets/winen15/overview
    vmss.go:390: [572.341s] Managed cluster portal link: https://ms.portal.azure.com/#@microsoft.onmicrosoft.com/resource/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/MC_abe2e-westus3_abe2e-azure-network-v3-f69fa_westus3/providers/Microsoft.ContainerService/managedClusters/abe2e-azure-network-v3-f69fa/overview
    vmss.go:509: [577.476s] VM will be automatically deleted after the test finishes, to preserve it for debugging purposes set KEEP_VMSS=true or pause the test with a breakpoint before the test finishes or failed
    vmss.go:513: [577.476s] SSH Instructions: (may take a few minutes for the VM to be ready for SSH)
        ========================
        az network bastion ssh --target-resource-id "/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/MC_abe2e-westus3_abe2e-azure-network-v3-f69fa_westus3/providers/Microsoft.Compute/virtualMachineScaleSets/winen15/virtualMachines/0" --name "abe2e-azure-network-v3-f69fa-bastion" --resource-group MC_abe2e-westus3_abe2e-azure-network-v3-f69fa_westus3 --auth-type ssh-key --username azureuser --ssh-key /tmp/private-key-2967649825
        
    bastionssh.go:304: [896.743s] Attempt 1/5 establishing SSH over bastion to 10.224.1.149
    vmss.go:563: [897.935s] VM reached running state
    vmss.go:533: [897.935s] βœ“ creating VMSS winen15 done (325.6s)
    test_helpers.go:461: [897.935s] saved Windows CSE output to scenario-logs/Test_Windows2025Gen2_WindowsCiliumNetworking/default/windows-cse-output.log
    kube.go:152: [897.935s] β†’ waiting for node winen15 to be ready...
    kube.go:174: [917.991s] node winen15000000 is ready. Taints: [{"key":"node.cloudprovider.kubernetes.io/uninitialized","value":"true","effect":"NoSchedule"}] Conditions: [{"type":"MemoryPressure","status":"False","lastHeartbeatTime":"2026-05-20T03:06:10Z","lastTransitionTime":"2026-05-20T03:06:09Z","reason":"KubeletHasSufficientMemory","message":"kubelet has sufficient memory available"},{"type":"DiskPressure","status":"False","lastHeartbeatTime":"2026-05-20T03:06:10Z","lastTransitionTime":"2026-05-20T03:06:09Z","reason":"KubeletHasNoDiskPressure","message":"kubelet has no disk pressure"},{"type":"PIDPressure","status":"False","lastHeartbeatTime":"2026-05-20T03:06:10Z","lastTransitionTime":"2026-05-20T03:06:09Z","reason":"KubeletHasSufficientPID","message":"kubelet has sufficient PID available"},{"type":"Ready","status":"True","lastHeartbeatTime":"2026-05-20T03:06:10Z","lastTransitionTime":"2026-05-20T03:06:10Z","reason":"KubeletReady","message":"kubelet is posting ready status"}]
    kube.go:195: [917.991s] βœ“ waiting for node winen15 to be ready done (20.1s)
    test_helpers.go:343: [917.991s] ⚠️ ##vso[task.logissue type=warning;] Node winen15 took 5m25.604933845s to be created and 20.055390452s to be ready
   
... [The stack trace has been truncated as it exceeded the maximum allowed size. Please refer to the complete log available in the Test Run attachments for full details.]

Check failure on line 1 in Test_Windows2025Gen2_WindowsCiliumNetworking

See this annotation in the file changed.

@azure-pipelines azure-pipelines / AKS Windows VHD Build - PR check-in gate

Test_Windows2025Gen2_WindowsCiliumNetworking

Failed
Raw output
=== RUN   Test_Windows2025Gen2_WindowsCiliumNetworking
=== PAUSE Test_Windows2025Gen2_WindowsCiliumNetworking
=== CONT  Test_Windows2025Gen2_WindowsCiliumNetworking
--- FAIL: Test_Windows2025Gen2_WindowsCiliumNetworking (0.00s)