[cherry-pick v20260318] fix(security): bump Go to 1.25.10 and golang.org/x/net to v0.55.0 #8556
Azure Pipelines / Agentbaker Windows E2E
failed
May 22, 2026 in 17m 47s
Build #20260522.6 had test failures
Details
- Failed: 1 (4.76%)
- Passed: 20 (95.24%)
- Other: 0 (0.00%)
- Total: 21
Annotations
Check failure on line 859 in Build log
azure-pipelines / Agentbaker Windows E2E
Build log #L859
Script failed with exit code: 1
Check failure on line 1 in Test_Windows2022_SecureTLSBootstrapping_BootstrapToken_Fallback
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
test_helpers.go:360: [5.411s] TAGS {Name:Test_Windows2022_SecureTLSBootstrapping_BootstrapToken_Fallback 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:199: [12.669s] → running scenario...
test_helpers.go:231: [17.722s] → preparing AKS node...
vmss.go:268: [30.294s] → creating VMSS winfq7m...
vmss.go:189: [30.320s] 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/winfq7m/overview
vmss.go:195: [30.320s] 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:301: [40.063s] 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:305: [40.063s] 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/winfq7m/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-2805943003
bastionssh.go:304: [238.098s] Attempt 1/5 establishing SSH over bastion to 10.224.1.120
vmss.go:355: [239.886s] VM reached running state
vmss.go:325: [239.886s] ✓ creating VMSS winfq7m done (209.6s)
test_helpers.go:420: [239.887s] saved Windows CSE output to scenario-logs/Test_Windows2022_SecureTLSBootstrapping_BootstrapToken_Fallback/windows-cse-output.log
kube.go:149: [239.887s] → waiting for node winfq7m to be ready...
kube.go:186: [264.323s] node winfq7m000000 is not ready. Taints: [{"key":"node.cloudprovider.kubernetes.io/uninitialized","value":"true","effect":"NoSchedule"},{"key":"node.kubernetes.io/not-ready","effect":"NoSchedule"}] Conditions: [{"type":"MemoryPressure","status":"False","lastHeartbeatTime":"2026-05-22T17:29:14Z","lastTransitionTime":"2026-05-22T17:29:14Z","reason":"KubeletHasSufficientMemory","message":"kubelet has sufficient memory available"},{"type":"DiskPressure","status":"False","lastHeartbeatTime":"2026-05-22T17:29:14Z","lastTransitionTime":"2026-05-22T17:29:14Z","reason":"KubeletHasNoDiskPressure","message":"kubelet has no disk pressure"},{"type":"PIDPressure","status":"False","lastHeartbeatTime":"2026-05-22T17:29:14Z","lastTransitionTime":"2026-05-22T17:29:14Z","reason":"KubeletHasSufficientPID","message":"kubelet has sufficient PID available"},{"type":"Ready","status":"False","lastHeartbeatTime":"2026-05-22T17:29:14Z","lastTransitionTime":"2026-05-22T17:29:14Z","reason":"KubeletNotReady","message":"CSINode is not yet initialized"}]
kube.go:186: [264.344s] node winfq7m000000 is not ready. Taints: [{"key":"node.cloudprovider.kubernetes.io/
... [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.]
Loading