Skip to content

fix(e2e): strict wireserver validation — fail fast on unexpected curl…

39773e4
Select commit
Loading
Failed to load commit list.
Merged

fix(e2e): strict wireserver validation — fail fast on unexpected curl exits #8580

fix(e2e): strict wireserver validation — fail fast on unexpected curl…
39773e4
Select commit
Loading
Failed to load commit list.
Azure Pipelines / Agentbaker E2E failed May 25, 2026 in 38m 0s

Build #20260525.2 had test failures

Details

Tests

  • Failed: 10 (2.28%)
  • Passed: 428 (97.72%)
  • Other: 0 (0.00%)
  • Total: 438

Annotations

Check failure on line 1816 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker E2E

Build log #L1816

Script failed with exit code: 1

Check failure on line 1 in Test_Ubuntu2204ARM64/default

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker E2E

Test_Ubuntu2204ARM64/default

Failed
Raw output
=== RUN   Test_Ubuntu2204ARM64/default
=== PAUSE Test_Ubuntu2204ARM64/default
=== CONT  Test_Ubuntu2204ARM64/default
    test_helpers.go:390: [0.000s] TAGS {Name:Test_Ubuntu2204ARM64/default ImageName:2204gen2arm64containerd OS:ubuntu Arch:arm64 NetworkIsolated:false NonAnonymousACR:false GPU:false WASM:false BootstrapTokenFallback:false KubeletCustomConfig:false Scriptless:false VHDCaching:false MockAzureChinaCloud:false VMSeriesCoverageTest:false}
    test_helpers.go:221: [0.000s] → running scenario...
    test_helpers.go:258: [0.000s] → preparing AKS node...
    vmss.go:476: [0.000s] → creating VMSS mbxc-2026-05-25-ubuntu2204arm64default...
    vmss.go:384: [0.214s] 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/mbxc-2026-05-25-ubuntu2204arm64default/overview
    vmss.go:390: [0.214s] 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
    vmss.go:509: [4.512s] 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: [4.512s] 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/mbxc-2026-05-25-ubuntu2204arm64default/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-1849039432
        
    bastionssh.go:304: [105.984s] Attempt 1/5 establishing SSH over bastion to 10.224.0.88
    vmss.go:563: [107.301s] VM reached running state
    vmss.go:533: [107.301s] ✓ creating VMSS mbxc-2026-05-25-ubuntu2204arm64default done (107.3s)
    kube.go:152: [107.301s] → waiting for node mbxc-2026-05-25-ubuntu2204arm64default to be ready...
    kube.go:174: [107.385s] node mbxc-2026-05-25-ubuntu2204arm64default000000 is ready. Taints: [{"key":"node.cloudprovider.kubernetes.io/uninitialized","value":"true","effect":"NoSchedule"}] Conditions: [{"type":"MemoryPressure","status":"False","lastHeartbeatTime":"2026-05-25T01:02:18Z","lastTransitionTime":"2026-05-25T01:02:16Z","reason":"KubeletHasSufficientMemory","message":"kubelet has sufficient memory available"},{"type":"DiskPressure","status":"False","lastHeartbeatTime":"2026-05-25T01:02:18Z","lastTransitionTime":"2026-05-25T01:02:16Z","reason":"KubeletHasNoDiskPressure","message":"kubelet has no disk pressure"},{"type":"PIDPressure","status":"False","lastHeartbeatTime":"2026-05-25T01:02:18Z","lastTransitionTime":"2026-05-25T01:02:16Z","reason":"KubeletHasSufficientPID","message":"kubelet has sufficient PID available"},{"type":"Ready","status":"True","lastHeartbeatTime":"2026-05-25T01:02:18Z","lastTransitionTime":"2026-05-25T01:02:18Z","reason":"KubeletReady","message":"kubelet is posting ready status"}]
    kube.go:195: [107.385s] ✓ waiting for node mbxc-2026-05-25-ubuntu2204arm64default to be ready done (0.1s)
    test_helpers.go:343: [107.385s] Node mbxc-2026-05-25-ubuntu2204arm64default took 1m47.300413804s to be created and 83.934773ms to be ready
    test_helpers.go:346: [107.385s] ✓ preparing AKS node done (107.4s)
    test_helpers.go:251
... [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_Ubuntu2204ARM64

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker E2E

Test_Ubuntu2204ARM64

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

Check failure on line 1 in Test_Ubuntu2204_DisableKubeletServingCertificateRotationWithTags_CustomKubeletConfig

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker E2E

Test_Ubuntu2204_DisableKubeletServingCertificateRotationWithTags_CustomKubeletConfig

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

Check failure on line 1 in Test_Ubuntu2204_DisableKubeletServingCertificateRotationWithTags_CustomKubeletConfig/default

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Agentbaker E2E

Test_Ubuntu2204_DisableKubeletServingCertificateRotationWithTags_CustomKubeletConfig/default

Failed
Raw output
=== RUN   Test_Ubuntu2204_DisableKubeletServingCertificateRotationWithTags_CustomKubeletConfig/default
=== PAUSE Test_Ubuntu2204_DisableKubeletServingCertificateRotationWithTags_CustomKubeletConfig/default
=== CONT  Test_Ubuntu2204_DisableKubeletServingCertificateRotationWithTags_CustomKubeletConfig/default
    test_helpers.go:390: [0.000s] TAGS {Name:Test_Ubuntu2204_DisableKubeletServingCertificateRotationWithTags_CustomKubeletConfig/default ImageName:2204gen2containerd OS:ubuntu 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: [0.000s] → running scenario...
    test_helpers.go:258: [0.001s] → preparing AKS node...
    vmss.go:476: [0.001s] → creating VMSS g9u3-2026-05-25-ubuntu2204disablekubeletservingcertificat...
    vmss.go:384: [0.248s] 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/g9u3-2026-05-25-ubuntu2204disablekubeletservingcertificat/overview
    vmss.go:390: [0.248s] 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
    vmss.go:509: [4.329s] 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: [4.329s] 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/g9u3-2026-05-25-ubuntu2204disablekubeletservingcertificat/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-1849039432
        
    bastionssh.go:304: [136.160s] Attempt 1/5 establishing SSH over bastion to 10.224.0.111
    vmss.go:563: [137.458s] VM reached running state
    vmss.go:533: [137.458s] ✓ creating VMSS g9u3-2026-05-25-ubuntu2204disablekubeletservingcertificat done (137.5s)
    kube.go:152: [137.458s] → waiting for node g9u3-2026-05-25-ubuntu2204disablekubeletservingcertificat to be ready...
    kube.go:174: [138.370s] node g9u3-2026-05-25-ubuntu2204disablekubeletservingcertificat000000 is 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-25T01:01:31Z","lastTransitionTime":"2026-05-25T01:01:08Z","reason":"KubeletHasSufficientMemory","message":"kubelet has sufficient memory available"},{"type":"DiskPressure","status":"False","lastHeartbeatTime":"2026-05-25T01:01:31Z","lastTransitionTime":"2026-05-25T01:01:08Z","reason":"KubeletHasNoDiskPressure","message":"kubelet has no disk pressure"},{"type":"PIDPressure","status":"False","lastHeartbeatTime":"2026-05-25T01:01:31Z","lastTransitionTime":"2026-05-25T01:01:08Z","reason":"KubeletHasSufficientPID","message":"kubelet has sufficient PID available"},{"type":"Ready","status":"True","lastHeartbeatTime":"2026-05-25T01:01:31Z","lastTransitionTime":"2026-05-25T0
... [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.]