Skip to content

chore(deps): update kubelet-kubectl (patch) #8494

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
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
+11 −11

chore(deps): update kubelet-kubectl

f059c94
Select commit
Loading
Failed to load commit list.
Open

chore(deps): update kubelet-kubectl (patch) #8494

chore(deps): update kubelet-kubectl
f059c94
Select commit
Loading
Failed to load commit list.
Azure Pipelines / AKS Windows VHD Build - PR check-in gate failed May 23, 2026 in 1h 33m 59s

Build #PR_20260523.12_merge_165352719 had test failures

2 errors / 3 warnings

Details

Tests

  • Failed: 4 (1.20%)
  • Passed: 328 (98.80%)
  • Other: 0 (0.00%)
  • Total: 332

Annotations

Check failure on line 1455 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / AKS Windows VHD Build - PR check-in gate

Build log #L1455 

Script failed with exit code: 1

Check failure on line 1480 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / AKS Windows VHD Build - PR check-in gate

Build log #L1480 

Script failed with exit code: 1

Check failure on line 1 in Test_Windows2022_VHDCaching/VHDCreation

See this annotation in the file changed.

@azure-pipelines azure-pipelines / AKS Windows VHD Build - PR check-in gate

Test_Windows2022_VHDCaching/VHDCreation 

Failed
Raw output 
=== RUN   Test_Windows2022_VHDCaching/VHDCreation
=== PAUSE Test_Windows2022_VHDCaching/VHDCreation
=== CONT  Test_Windows2022_VHDCaching/VHDCreation
    test_helpers.go:390: [426.151s] TAGS {Name:Test_Windows2022_VHDCaching/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: [433.003s] → running scenario...
    cluster.go:71: [433.003s] → preparing cluster...
    cluster.go:251: [433.003s] → get or create cluster abe2e-azure-network-v3-f69fa...
    cluster.go:259: [434.004s] ✓ get or create cluster abe2e-azure-network-v3-f69fa done (1.0s)
    cluster.go:835: [434.004s] → setting up private DNS for API server...
    aks_model.go:307: [436.505s] → adding firewall rules...
    aks_model.go:336: [438.373s] Creating subnet AzureFirewallSubnet in VNet aks-vnet-30633331
    aks_model.go:355: [438.878s] 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: [438.878s] Creating public IP abe2e-fw-pip
    cluster.go:874: [439.417s] private DNS zone "abe2e-azure-network-v3-vvz2js56.hcp.westus3.azmk8s.io" → [4.242.145.58]
    cluster.go:875: [439.417s] ✓ setting up private DNS for API server done (5.4s)
    aks_model.go:387: [439.952s] 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: [439.952s] Firewall rules configured successfully
    aks_model.go:405: [441.034s] Firewall private IP: 10.225.0.4
    aks_model.go:436: [441.034s] Adding route "vnet-local" to AKS route table "abe2e-fw-rt"
    aks_model.go:436: [442.136s] Adding route "default-route-to-firewall" to AKS route table "abe2e-fw-rt"
    aks_model.go:447: [442.770s] Successfully added firewall routes to AKS route table "abe2e-fw-rt"
    aks_model.go:448: [442.770s] ✓ adding firewall rules done (6.3s)
    kube.go:379: [442.770s] Creating daemonset debug-mariner-tolerated with image mcr.microsoft.com/cbl-mariner/base/core:2.0
    cluster.go:727: [442.770s] → collecting garbage VMSS...
    kube.go:379: [442.901s] Creating daemonset debugnonhost-mariner-tolerated with image mcr.microsoft.com/cbl-mariner/base/core:2.0
    kube.go:561: [442.967s] Creating proxy daemonset e2e-proxy with image mcr.microsoft.com/cbl-mariner/base/python:3
    cluster.go:777: [443.441s] → collecting garbage K8s nodes...
    cluster.go:811: [443.477s] ✓ collecting garbage K8s nodes done (0.0s)
    cluster.go:769: [443.477s] ✓ collecting garbage VMSS done (0.7s)
    cluster.go:133: [443.477s] ✓ preparing cluster done (10.5s)
    test_helpers.go:258: [443.477s] → preparing AKS node...
    vmss.go:476: [453.043s] → creating VMSS winttpv...
    vmss.go:384: [453.047s] 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/winttpv/overview
    vmss.go:390: [453.048s] 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: [457.951s] VM will be automatically dele
... [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

See this annotation in the file changed.

@azure-pipelines azure-pipelines / AKS Windows VHD Build - PR check-in gate

Test_Windows2022_VHDCaching 

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

Check failure on line 1 in Test_Windows2025Gen2

See this annotation in the file changed.

@azure-pipelines azure-pipelines / AKS Windows VHD Build - PR check-in gate

Test_Windows2025Gen2 

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

Check failure on line 1 in Test_Windows2025Gen2/default

See this annotation in the file changed.

@azure-pipelines azure-pipelines / AKS Windows VHD Build - PR check-in gate

Test_Windows2025Gen2/default 

Failed
Raw output 
=== RUN   Test_Windows2025Gen2/default
=== PAUSE Test_Windows2025Gen2/default
=== CONT  Test_Windows2025Gen2/default
    test_helpers.go:390: [485.715s] TAGS {Name:Test_Windows2025Gen2/default ImageName:windows-2025-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: [491.253s] → running scenario...
    test_helpers.go:258: [500.070s] → preparing AKS node...
    vmss.go:476: [513.625s] → creating VMSS win8kjp...
    vmss.go:384: [513.630s] 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/win8kjp/overview
    vmss.go:390: [513.630s] 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: [518.708s] 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: [518.708s] 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/win8kjp/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-1723642047
        
    bastionssh.go:304: [716.870s] Attempt 1/5 establishing SSH over bastion to 10.224.0.193
    vmss.go:563: [718.292s] VM reached running state
    vmss.go:533: [718.292s] ✓ creating VMSS win8kjp done (204.7s)
    test_helpers.go:461: [718.292s] saved Windows CSE output to scenario-logs/Test_Windows2025Gen2/default/windows-cse-output.log
    kube.go:152: [718.292s] → waiting for node win8kjp to be ready...
    kube.go:174: [718.418s] node win8kjp000000 is ready. Taints: null Conditions: [{"type":"MemoryPressure","status":"False","lastHeartbeatTime":"2026-05-23T22:23:41Z","lastTransitionTime":"2026-05-23T22:23:41Z","reason":"KubeletHasSufficientMemory","message":"kubelet has sufficient memory available"},{"type":"DiskPressure","status":"False","lastHeartbeatTime":"2026-05-23T22:23:41Z","lastTransitionTime":"2026-05-23T22:23:41Z","reason":"KubeletHasNoDiskPressure","message":"kubelet has no disk pressure"},{"type":"PIDPressure","status":"False","lastHeartbeatTime":"2026-05-23T22:23:41Z","lastTransitionTime":"2026-05-23T22:23:41Z","reason":"KubeletHasSufficientPID","message":"kubelet has sufficient PID available"},{"type":"Ready","status":"True","lastHeartbeatTime":"2026-05-23T22:23:41Z","lastTransitionTime":"2026-05-23T22:23:41Z","reason":"KubeletReady","message":"kubelet is posting ready status"}]
    kube.go:195: [718.418s] ✓ waiting for node win8kjp to be ready done (0.1s)
    test_helpers.go:343: [718.418s] ⚠️ ##vso[task.logissue type=warning;] Node win8kjp took 3m24.667163454s to be created and 126.045567ms to be ready
    test_helpers.go:346: [718.418s] ✓ preparing AKS node done (218.3s)
    test_helpers.go:251: [718.418s] Choosing the private ACR "abe2eprivatewestus3" for the vm validation
    test_helpers.go:410: [718.418s] → va
... [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