Skip to content

feat: windows-exporter into windows vhd build #8516

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.

Sign up for GitHub

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

Open
chmill-zz wants to merge 6 commits into
base: main
Choose a base branch
from

out of scope

b533a02
Select commit
Loading
Failed to load commit list.
Open

feat: windows-exporter into windows vhd build #8516

out of scope
b533a02
Select commit
Loading
Failed to load commit list.
Azure Pipelines / Agentbaker GPU E2E failed May 20, 2026 in 21m 31s

Build #20260519.8 had test failures

1 errors / 3 warnings

Details

Tests

  • Failed: 12 (1.97%)
  • Passed: 597 (98.03%)
  • Other: 0 (0.00%)
  • Total: 609

Annotations

Check failure on line 1745 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker GPU E2E

Build log #L1745 

Script failed with exit code: 1

Check failure on line 1 in Test_AzureLinux3_NvidiaDevicePluginRunning/scriptless_nbc

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker GPU E2E

Test_AzureLinux3_NvidiaDevicePluginRunning/scriptless_nbc 

Failed
Raw output 
=== RUN   Test_AzureLinux3_NvidiaDevicePluginRunning/scriptless_nbc
=== PAUSE Test_AzureLinux3_NvidiaDevicePluginRunning/scriptless_nbc
=== CONT  Test_AzureLinux3_NvidiaDevicePluginRunning/scriptless_nbc
    test_helpers.go:390: [8.156s] TAGS {Name:Test_AzureLinux3_NvidiaDevicePluginRunning/scriptless_nbc ImageName:AzureLinuxV3gen2 OS:azurelinux Arch:amd64 NetworkIsolated:false NonAnonymousACR:false GPU:true WASM:false BootstrapTokenFallback:false KubeletCustomConfig:false Scriptless:false VHDCaching:false MockAzureChinaCloud:false VMSeriesCoverageTest:false}
    test_helpers.go:221: [16.565s] → running scenario...
    test_helpers.go:258: [23.985s] → preparing AKS node...
    vmss.go:476: [38.106s] → creating VMSS cixq-2026-05-19-azurelinux3nvidiadevicepluginrunningscrip...
    vmss.go:384: [56.362s] VMSS portal link: https://ms.portal.azure.com/#@microsoft.onmicrosoft.com/resource/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/MC_abe2e-westus3_abe2e-kubenet-v4-e1f58_westus3/providers/Microsoft.Compute/virtualMachineScaleSets/cixq-2026-05-19-azurelinux3nvidiadevicepluginrunningscrip/overview
    vmss.go:390: [56.362s] Managed cluster portal link: https://ms.portal.azure.com/#@microsoft.onmicrosoft.com/resource/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/MC_abe2e-westus3_abe2e-kubenet-v4-e1f58_westus3/providers/Microsoft.ContainerService/managedClusters/abe2e-kubenet-v4-e1f58/overview
2026/05/19 21:50:31 Using VM extension version 1.439 for extension type Compute.AKS.Linux.AKSNode in region westus3
    vmss.go:509: [62.833s] 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: [62.834s] 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-kubenet-v4-e1f58_westus3/providers/Microsoft.Compute/virtualMachineScaleSets/cixq-2026-05-19-azurelinux3nvidiadevicepluginrunningscrip/virtualMachines/0" --name "abe2e-kubenet-v4-e1f58-bastion" --resource-group MC_abe2e-westus3_abe2e-kubenet-v4-e1f58_westus3 --auth-type ssh-key --username azureuser --ssh-key /tmp/private-key-244205180
        
    bastionssh.go:304: [285.302s] Attempt 1/5 establishing SSH over bastion to 10.224.0.12
    vmss.go:563: [287.071s] VM reached running state
    vmss.go:533: [287.071s] ✓ creating VMSS cixq-2026-05-19-azurelinux3nvidiadevicepluginrunningscrip done (249.0s)
    kube.go:152: [287.072s] → waiting for node cixq-2026-05-19-azurelinux3nvidiadevicepluginrunningscrip to be ready...
    kube.go:174: [287.118s] node cixq-2026-05-19-azurelinux3nvidiadevicepluginrunningscrip000000 is ready. Taints: [{"key":"node.kubernetes.io/network-unavailable","effect":"NoSchedule","timeAdded":"2026-05-19T21:53:55Z"}] Conditions: [{"type":"FrequentContainerdRestart","status":"False","lastHeartbeatTime":"2026-05-19T21:54:06Z","lastTransitionTime":"2026-05-19T21:54:05Z","reason":"NoFrequentContainerdRestart","message":"containerd is functioning properly"},{"type":"ContainerRuntimeProblem","status":"False","lastHeartbeatTime":"2026-05-19T21:54:06Z","lastTransitionTime":"2026-05-19T21:54:05Z","reason":"ContainerRuntimeIsUp","message":"container runtime service is up"},{"type":"KernelDeadlock","status":"False","lastHeartbeatTime":"2026-05-19T21:54:06Z","lastTransitionTime":"2026-05-19T21:54:05Z","reason":"KernelHasNoDeadlock","message":"kernel has no deadlock"},{"type":"GPUMissing","status":"False","lastHeartbeatTime":"2026-05-19T21:54:06Z","lastTransitionTime":"2026-05-19T21:54:05Z","reason":"NoGPUMissing","message":"All GPUs are p
... [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_AzureLinux3_NvidiaDevicePluginRunning/default

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker GPU E2E

Test_AzureLinux3_NvidiaDevicePluginRunning/default 

Failed
Raw output 
=== RUN   Test_AzureLinux3_NvidiaDevicePluginRunning/default
=== PAUSE Test_AzureLinux3_NvidiaDevicePluginRunning/default
=== CONT  Test_AzureLinux3_NvidiaDevicePluginRunning/default
    test_helpers.go:390: [8.156s] TAGS {Name:Test_AzureLinux3_NvidiaDevicePluginRunning/default ImageName:AzureLinuxV3gen2 OS:azurelinux Arch:amd64 NetworkIsolated:false NonAnonymousACR:false GPU:true WASM:false BootstrapTokenFallback:false KubeletCustomConfig:false Scriptless:false VHDCaching:false MockAzureChinaCloud:false VMSeriesCoverageTest:false}
    test_helpers.go:221: [16.561s] → running scenario...
    test_helpers.go:258: [23.985s] → preparing AKS node...
    vmss.go:476: [38.049s] → creating VMSS 9xuc-2026-05-19-azurelinux3nvidiadevicepluginrunningdefau...
    vmss.go:384: [41.162s] VMSS portal link: https://ms.portal.azure.com/#@microsoft.onmicrosoft.com/resource/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/MC_abe2e-westus3_abe2e-kubenet-v4-e1f58_westus3/providers/Microsoft.Compute/virtualMachineScaleSets/9xuc-2026-05-19-azurelinux3nvidiadevicepluginrunningdefau/overview
    vmss.go:390: [41.162s] Managed cluster portal link: https://ms.portal.azure.com/#@microsoft.onmicrosoft.com/resource/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/MC_abe2e-westus3_abe2e-kubenet-v4-e1f58_westus3/providers/Microsoft.ContainerService/managedClusters/abe2e-kubenet-v4-e1f58/overview
2026/05/19 21:50:16 Using VM extension version 1.439 for extension type Compute.AKS.Linux.AKSNode in region westus3
    vmss.go:509: [50.177s] 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: [50.178s] 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-kubenet-v4-e1f58_westus3/providers/Microsoft.Compute/virtualMachineScaleSets/9xuc-2026-05-19-azurelinux3nvidiadevicepluginrunningdefau/virtualMachines/0" --name "abe2e-kubenet-v4-e1f58-bastion" --resource-group MC_abe2e-westus3_abe2e-kubenet-v4-e1f58_westus3 --auth-type ssh-key --username azureuser --ssh-key /tmp/private-key-244205180
        
    bastionssh.go:304: [302.787s] Attempt 1/5 establishing SSH over bastion to 10.224.0.107
    vmss.go:563: [304.166s] VM reached running state
    vmss.go:533: [304.166s] ✓ creating VMSS 9xuc-2026-05-19-azurelinux3nvidiadevicepluginrunningdefau done (266.1s)
    kube.go:152: [304.166s] → waiting for node 9xuc-2026-05-19-azurelinux3nvidiadevicepluginrunningdefau to be ready...
    kube.go:174: [304.203s] node 9xuc-2026-05-19-azurelinux3nvidiadevicepluginrunningdefau000000 is ready. Taints: [{"key":"node.cloudprovider.kubernetes.io/uninitialized","value":"true","effect":"NoSchedule"}] Conditions: [{"type":"FrequentUnregisterNetDevice","status":"False","lastHeartbeatTime":"2026-05-19T21:54:27Z","lastTransitionTime":"2026-05-19T21:53:43Z","reason":"NoFrequentUnregisterNetDevice","message":"node is functioning properly"},{"type":"FrequentDockerRestart","status":"False","lastHeartbeatTime":"2026-05-19T21:54:27Z","lastTransitionTime":"2026-05-19T21:53:43Z","reason":"NoFrequentDockerRestart","message":"docker is functioning properly"},{"type":"ReadonlyFilesystem","status":"False","lastHeartbeatTime":"2026-05-19T21:54:27Z","lastTransitionTime":"2026-05-19T21:53:43Z","reason":"FilesystemIsNotReadOnly","message":"Filesystem is not read-only"},{"type":"ContainerRuntimeProblem","status":"False","lastHeartbeatTime":"2026-05-19T21:54:27Z","lastTransitionTime":"2026-05-19T21:53:43Z","reason":"ContainerRuntimeIsUp","message":"container runtime ser
... [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_AzureLinux3_NvidiaDevicePluginRunning

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker GPU E2E

Test_AzureLinux3_NvidiaDevicePluginRunning 

Failed
Raw output 
=== RUN   Test_AzureLinux3_NvidiaDevicePluginRunning
=== PAUSE Test_AzureLinux3_NvidiaDevicePluginRunning
=== CONT  Test_AzureLinux3_NvidiaDevicePluginRunning
--- FAIL: Test_AzureLinux3_NvidiaDevicePluginRunning (0.01s)

Check failure on line 1 in Test_AzureLinux3_NvidiaDevicePluginRunning/scriptless_nbc

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker GPU E2E

Test_AzureLinux3_NvidiaDevicePluginRunning/scriptless_nbc 

Failed
Raw output 
=== RUN   Test_AzureLinux3_NvidiaDevicePluginRunning/scriptless_nbc
=== PAUSE Test_AzureLinux3_NvidiaDevicePluginRunning/scriptless_nbc
=== CONT  Test_AzureLinux3_NvidiaDevicePluginRunning/scriptless_nbc
    test_helpers.go:390: [8.231s] TAGS {Name:Test_AzureLinux3_NvidiaDevicePluginRunning/scriptless_nbc ImageName:AzureLinuxV3gen2 OS:azurelinux Arch:amd64 NetworkIsolated:false NonAnonymousACR:false GPU:true WASM:false BootstrapTokenFallback:false KubeletCustomConfig:false Scriptless:false VHDCaching:false MockAzureChinaCloud:false VMSeriesCoverageTest:false}
    test_helpers.go:221: [15.908s] → running scenario...
    test_helpers.go:258: [25.418s] → preparing AKS node...
    vmss.go:476: [37.722s] → creating VMSS tk5s-2026-05-19-azurelinux3nvidiadevicepluginrunningscrip...
    vmss.go:384: [53.886s] VMSS portal link: https://ms.portal.azure.com/#@microsoft.onmicrosoft.com/resource/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/MC_abe2e-westus3_abe2e-kubenet-v4-e1f58_westus3/providers/Microsoft.Compute/virtualMachineScaleSets/tk5s-2026-05-19-azurelinux3nvidiadevicepluginrunningscrip/overview
    vmss.go:390: [53.894s] Managed cluster portal link: https://ms.portal.azure.com/#@microsoft.onmicrosoft.com/resource/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/MC_abe2e-westus3_abe2e-kubenet-v4-e1f58_westus3/providers/Microsoft.ContainerService/managedClusters/abe2e-kubenet-v4-e1f58/overview
2026/05/19 22:37:40 Using VM extension version 1.439 for extension type Compute.AKS.Linux.AKSNode in region westus3
    vmss.go:509: [62.286s] 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: [62.286s] 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-kubenet-v4-e1f58_westus3/providers/Microsoft.Compute/virtualMachineScaleSets/tk5s-2026-05-19-azurelinux3nvidiadevicepluginrunningscrip/virtualMachines/0" --name "abe2e-kubenet-v4-e1f58-bastion" --resource-group MC_abe2e-westus3_abe2e-kubenet-v4-e1f58_westus3 --auth-type ssh-key --username azureuser --ssh-key /tmp/private-key-1245556324
        
    bastionssh.go:304: [285.819s] Attempt 1/5 establishing SSH over bastion to 10.224.0.121
    vmss.go:563: [287.257s] VM reached running state
    vmss.go:533: [287.257s] ✓ creating VMSS tk5s-2026-05-19-azurelinux3nvidiadevicepluginrunningscrip done (249.5s)
    kube.go:152: [287.257s] → waiting for node tk5s-2026-05-19-azurelinux3nvidiadevicepluginrunningscrip to be ready...
    kube.go:174: [287.293s] node tk5s-2026-05-19-azurelinux3nvidiadevicepluginrunningscrip000000 is ready. Taints: [{"key":"node.kubernetes.io/network-unavailable","effect":"NoSchedule","timeAdded":"2026-05-19T22:41:08Z"}] Conditions: [{"type":"NetworkUnavailable","status":"True","lastHeartbeatTime":"2026-05-19T22:41:08Z","lastTransitionTime":"2026-05-19T22:41:08Z","reason":"NodeInitialization","message":"Waiting for cloud routes"},{"type":"VMEventScheduled","status":"Unknown","lastHeartbeatTime":"2026-05-19T22:41:29Z","lastTransitionTime":"2026-05-19T22:41:29Z","reason":"NoVMEventScheduled","message":"Unable to verify scheduled events (IMDS unavailable)"},{"type":"FrequentKubeletRestart","status":"False","lastHeartbeatTime":"2026-05-19T22:41:29Z","lastTransitionTime":"2026-05-19T22:41:05Z","reason":"NoFrequentKubeletRestart","message":"kubelet is functioning properly"},{"type":"FrequentUnregisterNetDevice","status":"False","lastHeartbeatTime":"2026-05-19T22:41:29Z","lastTransitionTime":"2026-05-19T22:41:05Z","reason":"NoFrequentU
... [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.]
View more details on Azure Pipelines