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 Windows E2E failed May 21, 2026 in 12m 56s

Build #20260519.7 had test failures

1 errors / 6 warnings

Details

Tests

  • Failed: 74 (4.03%)
  • Passed: 1,763 (95.97%)
  • Other: 0 (0.00%)
  • Total: 1,837

Annotations

Check failure on line 1707 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker Windows E2E

Build log #L1707 

Script failed with exit code: 1

Check failure on line 1 in Test_Windows2022_SecureTLSBootstrapping_BootstrapToken_Fallback/default

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker Windows E2E

Test_Windows2022_SecureTLSBootstrapping_BootstrapToken_Fallback/default 

Failed
Raw output 
=== RUN   Test_Windows2022_SecureTLSBootstrapping_BootstrapToken_Fallback/default
=== PAUSE Test_Windows2022_SecureTLSBootstrapping_BootstrapToken_Fallback/default
=== CONT  Test_Windows2022_SecureTLSBootstrapping_BootstrapToken_Fallback/default
    test_helpers.go:390: [6.246s] TAGS {Name:Test_Windows2022_SecureTLSBootstrapping_BootstrapToken_Fallback/default ImageName:windows-2022-containerd-gen2 OS:windows Arch:amd64 NetworkIsolated:false NonAnonymousACR:false GPU:false WASM:false BootstrapTokenFallback:true KubeletCustomConfig:false Scriptless:false VHDCaching:false MockAzureChinaCloud:false VMSeriesCoverageTest:false}
    test_helpers.go:221: [12.454s] → running scenario...
    test_helpers.go:258: [23.621s] → preparing AKS node...
    vmss.go:476: [35.755s] → creating VMSS win733n...
    vmss.go:384: [35.828s] 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/win733n/overview
    vmss.go:390: [35.855s] 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: [45.223s] 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: [45.223s] 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/win733n/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-1132230594
        
    bastionssh.go:304: [273.764s] Attempt 1/5 establishing SSH over bastion to 10.224.0.131
    vmss.go:563: [275.023s] VM reached running state
    vmss.go:533: [275.023s] ✓ creating VMSS win733n done (239.3s)
    test_helpers.go:461: [275.023s] saved Windows CSE output to scenario-logs/Test_Windows2022_SecureTLSBootstrapping_BootstrapToken_Fallback/default/windows-cse-output.log
    kube.go:152: [275.023s] → waiting for node win733n to be ready...
    kube.go:174: [315.064s] node win733n000000 is ready. Taints: [{"key":"node.cloudprovider.kubernetes.io/uninitialized","value":"true","effect":"NoSchedule"}] Conditions: [{"type":"MemoryPressure","status":"False","lastHeartbeatTime":"2026-05-19T21:54:38Z","lastTransitionTime":"2026-05-19T21:54:38Z","reason":"KubeletHasSufficientMemory","message":"kubelet has sufficient memory available"},{"type":"DiskPressure","status":"False","lastHeartbeatTime":"2026-05-19T21:54:38Z","lastTransitionTime":"2026-05-19T21:54:38Z","reason":"KubeletHasNoDiskPressure","message":"kubelet has no disk pressure"},{"type":"PIDPressure","status":"False","lastHeartbeatTime":"2026-05-19T21:54:38Z","lastTransitionTime":"2026-05-19T21:54:38Z","reason":"KubeletHasSufficientPID","message":"kubelet has sufficient PID available"},{"type":"Ready","status":"True","lastHeartbeatTime":"2026-05-19T21:54:38Z","lastTransitionTime":"2026-05-19T21:54:38Z","reason":"KubeletReady","message":"kubelet is posting ready status"}]
    kube.go:195: [315.064s] ✓ waiting for node win733n to be ready done (40.0s)
    test_helpers.go:343: [315.064s] ⚠️ ##vso[task.logissue 
... [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_Windows2022_SecureTLSBootstrapping_BootstrapToken_Fallback

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker Windows E2E

Test_Windows2022_SecureTLSBootstrapping_BootstrapToken_Fallback 

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

Check failure on line 1 in Test_Windows2022Gen2AzureNetwork

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker Windows E2E

Test_Windows2022Gen2AzureNetwork 

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

Check failure on line 1 in Test_Windows2022Gen2AzureNetwork/default

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker Windows E2E

Test_Windows2022Gen2AzureNetwork/default 

Failed
Raw output 
=== RUN   Test_Windows2022Gen2AzureNetwork/default
=== PAUSE Test_Windows2022Gen2AzureNetwork/default
=== CONT  Test_Windows2022Gen2AzureNetwork/default
    test_helpers.go:390: [5.238s] TAGS {Name:Test_Windows2022Gen2AzureNetwork/default ImageName:windows-2022-containerd-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: [12.303s] → running scenario...
    cluster.go:71: [12.303s] → preparing cluster...
    cluster.go:251: [12.306s] → get or create cluster abe2e-azure-network-v3-f69fa...
    cluster.go:259: [13.256s] ✓ get or create cluster abe2e-azure-network-v3-f69fa done (0.9s)
    cluster.go:835: [13.256s] → setting up private DNS for API server...
    aks_model.go:307: [13.995s] → adding firewall rules...
    aks_model.go:336: [16.635s] Creating subnet AzureFirewallSubnet in VNet aks-vnet-30633331
    aks_model.go:355: [17.125s] Created firewall subnet with ID: /subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/MC_abe2e-westus3_abe2e-azure-network-v3-f69fa_westus3/providers/Microsoft.Network/virtualNetworks/aks-vnet-30633331/subnets/AzureFirewallSubnet
    aks_model.go:369: [17.125s] Creating public IP abe2e-fw-pip
    aks_model.go:387: [18.476s] Created public IP with ID: /subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/MC_abe2e-westus3_abe2e-azure-network-v3-f69fa_westus3/providers/Microsoft.Network/publicIPAddresses/abe2e-fw-pip
    aks_model.go:291: [18.476s] Firewall rules configured successfully
    cluster.go:874: [19.668s] private DNS zone "abe2e-azure-network-v3-aerxlfrv.hcp.westus3.azmk8s.io" → [4.249.31.40]
    cluster.go:875: [19.668s] ✓ setting up private DNS for API server done (6.4s)
    aks_model.go:405: [20.720s] Firewall private IP: 10.225.0.4
    aks_model.go:436: [20.720s] Adding route "vnet-local" to AKS route table "abe2e-fw-rt"
    aks_model.go:436: [21.938s] Adding route "default-route-to-firewall" to AKS route table "abe2e-fw-rt"
    aks_model.go:447: [22.976s] Successfully added firewall routes to AKS route table "abe2e-fw-rt"
    aks_model.go:448: [22.976s] ✓ adding firewall rules done (9.0s)
    cluster.go:727: [22.976s] → collecting garbage VMSS...
    kube.go:379: [22.976s] Creating daemonset debug-mariner-tolerated with image mcr.microsoft.com/cbl-mariner/base/core:2.0
    kube.go:379: [23.088s] Creating daemonset debugnonhost-mariner-tolerated with image mcr.microsoft.com/cbl-mariner/base/core:2.0
    kube.go:561: [23.154s] Creating proxy daemonset e2e-proxy with image mcr.microsoft.com/cbl-mariner/base/python:3
    cluster.go:777: [23.677s] → collecting garbage K8s nodes...
    cluster.go:811: [23.718s] ✓ collecting garbage K8s nodes done (0.0s)
    cluster.go:769: [23.718s] ✓ collecting garbage VMSS done (0.7s)
    cluster.go:133: [23.718s] ✓ preparing cluster done (11.4s)
    test_helpers.go:258: [23.718s] → preparing AKS node...
    vmss.go:476: [36.759s] → creating VMSS wintxc4...
    vmss.go:384: [36.852s] 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/wintxc4/overview
    vmss.go:390: [36.852s] 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: [47.024s] VM will be automatically deleted after the test finis
... [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