fix(e2e): reduce E2E test flakiness (sandbox events, duplicate CSE timing) #8480
+18
−46
Azure Pipelines / Agentbaker Windows E2E
failed
May 25, 2026 in 29m 3s
Build #20260525.2 had test failures
Details
- Failed: 3 (1.67%)
- Passed: 177 (98.33%)
- Other: 0 (0.00%)
- Total: 180
Annotations
Check failure on line 1490 in Build log
azure-pipelines / Agentbaker Windows E2E
Build log #L1490
Script failed with exit code: 1
Check failure on line 1 in Test_Windows2022_VHDCaching_LegacyTLSBootstrap/VHDCreation
azure-pipelines / Agentbaker Windows E2E
Test_Windows2022_VHDCaching_LegacyTLSBootstrap/VHDCreation
Failed
Raw output
=== RUN Test_Windows2022_VHDCaching_LegacyTLSBootstrap/VHDCreation
=== PAUSE Test_Windows2022_VHDCaching_LegacyTLSBootstrap/VHDCreation
=== CONT Test_Windows2022_VHDCaching_LegacyTLSBootstrap/VHDCreation
test_helpers.go:390: [6.142s] TAGS {Name:Test_Windows2022_VHDCaching_LegacyTLSBootstrap/VHDCreation ImageName:windows-2022-containerd OS:windows Arch:amd64 NetworkIsolated:false NonAnonymousACR:false GPU:false WASM:false BootstrapTokenFallback:false KubeletCustomConfig:false Scriptless:false VHDCaching:true MockAzureChinaCloud:false VMSeriesCoverageTest:false}
test_helpers.go:221: [10.898s] → running scenario...
test_helpers.go:258: [20.687s] → preparing AKS node...
vmss.go:476: [33.711s] → creating VMSS winx6ob...
vmss.go:384: [33.744s] 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/winx6ob/overview
vmss.go:390: [33.744s] 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: [43.509s] 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: [43.509s] 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/winx6ob/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-1449837604
bastionssh.go:304: [180.810s] Attempt 1/5 establishing SSH over bastion to 10.224.3.133
vmss.go:563: [182.356s] VM reached running state
vmss.go:533: [182.357s] ✓ creating VMSS winx6ob done (148.6s)
test_helpers.go:461: [182.357s] saved Windows CSE output to scenario-logs/Test_Windows2022_VHDCaching_LegacyTLSBootstrap/VHDCreation/windows-cse-output.log
test_helpers.go:346: [182.357s] ✓ preparing AKS node done (161.7s)
test_helpers.go:251: [182.357s] Choosing the private ACR "abe2eprivatewestus3" for the vm validation
test_helpers.go:410: [182.357s] → validating VM...
test_helpers.go:825: [184.811s] SSH connectivity to 10.224.3.133 verified successfully
test_helpers.go:123: [185.451s] stdout:
stderr:
test_helpers.go:124: [186.036s] stdout:
stderr:
test_helpers.go:134: === Creating VHD Image ===
test_helpers.go:635: [187.239s] Running sysprep on Windows VM...
test_helpers.go:610: [248.036s] Command "C:\\Windows\\System32\\Sysprep\\Sysprep.exe /oobe /generalize /mode:vm /quiet /quit;" took 1m0.796910775s
test_helpers.go:638: [248.037s] Sysprep result: {
"value": [
{
"code": "ComponentStatus/StdOut/succeeded",
"displayStatus": "Provisioning succeeded",
"level": "Info",
"message": ""
},
{
"code": "ComponentStatus/StdErr/succeeded",
"displayStatus": "Provisioning succeeded",
"level": "Info",
"message": ""
}
]
}
test_helpers.go:645: [248.100s] Deallocating VMSS VM..
... [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_VHDCaching_LegacyTLSBootstrap
azure-pipelines / Agentbaker Windows E2E
Test_Windows2022_VHDCaching_LegacyTLSBootstrap
Failed
Raw output
=== RUN Test_Windows2022_VHDCaching_LegacyTLSBootstrap
=== PAUSE Test_Windows2022_VHDCaching_LegacyTLSBootstrap
=== CONT Test_Windows2022_VHDCaching_LegacyTLSBootstrap
--- FAIL: Test_Windows2022_VHDCaching_LegacyTLSBootstrap (0.00s)
Loading