Skip to content

fix(security): bump Go to 1.25.10 and golang.org/x/net to v0.55.0

02e347c
Select commit
Loading
Failed to load commit list.
Open

[cherry-pick v20260413] fix(security): bump Go to 1.25.10 and golang.org/x/net to v0.55.0 #8569

fix(security): bump Go to 1.25.10 and golang.org/x/net to v0.55.0
02e347c
Select commit
Loading
Failed to load commit list.
Azure Pipelines / Agentbaker Windows E2E failed May 22, 2026 in 17m 2s

Build #20260522.12 had test failures

Details

Tests

  • Failed: 1 (3.57%)
  • Passed: 27 (96.43%)
  • Other: 0 (0.00%)
  • Total: 28

Annotations

Check failure on line 918 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker Windows E2E

Build log #L918

Script failed with exit code: 1

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
    test_helpers.go:361: [4.883s] 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:200: [11.796s] → running scenario...
    test_helpers.go:232: [16.312s] → preparing AKS node...
    vmss.go:324: [27.748s] → creating VMSS win0k7z...
    vmss.go:232: [27.836s] 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/win0k7z/overview
    vmss.go:238: [27.836s] 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:357: [40.238s] 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:361: [40.238s] 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/win0k7z/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-3341172730
        
    bastionssh.go:304: [208.161s] Attempt 1/5 establishing SSH over bastion to 10.224.3.59
    vmss.go:411: [210.079s] VM reached running state
    vmss.go:381: [210.079s] ✓ creating VMSS win0k7z done (182.3s)
    test_helpers.go:421: [210.079s] saved Windows CSE output to scenario-logs/Test_Windows2022_SecureTLSBootstrapping_BootstrapToken_Fallback/windows-cse-output.log
    kube.go:150: [210.079s] → waiting for node win0k7z to be ready...
    kube.go:172: [260.139s] node win0k7z000000 is ready. Taints: [{"key":"node.cloudprovider.kubernetes.io/uninitialized","value":"true","effect":"NoSchedule"}] Conditions: [{"type":"MemoryPressure","status":"False","lastHeartbeatTime":"2026-05-22T17:52:25Z","lastTransitionTime":"2026-05-22T17:52:24Z","reason":"KubeletHasSufficientMemory","message":"kubelet has sufficient memory available"},{"type":"DiskPressure","status":"False","lastHeartbeatTime":"2026-05-22T17:52:25Z","lastTransitionTime":"2026-05-22T17:52:24Z","reason":"KubeletHasNoDiskPressure","message":"kubelet has no disk pressure"},{"type":"PIDPressure","status":"False","lastHeartbeatTime":"2026-05-22T17:52:25Z","lastTransitionTime":"2026-05-22T17:52:24Z","reason":"KubeletHasSufficientPID","message":"kubelet has sufficient PID available"},{"type":"Ready","status":"True","lastHeartbeatTime":"2026-05-22T17:52:25Z","lastTransitionTime":"2026-05-22T17:52:25Z","reason":"KubeletReady","message":"kubelet is posting ready status"}]
    kube.go:193: [260.139s] ✓ waiting for node win0k7z to be ready done (50.1s)
    test_helpers.go:314: [260.139s] ⚠️ ##vso[task.logissue type=warning;] Node win0k7z took 3m2.3308
... [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.]