Skip to content

chore(deps): update azuremonitor/containerinsights/ciprod docker tag …

2435d87
Select commit
Loading
Failed to load commit list.
Open

chore(deps): update azuremonitor/containerinsights/ciprod docker tag to v3.4.0 #8548

chore(deps): update azuremonitor/containerinsights/ciprod docker tag …
2435d87
Select commit
Loading
Failed to load commit list.
Azure Pipelines / AKS Windows VHD Build - PR check-in gate failed May 21, 2026 in 1h 40m 3s

Build #PR_20260521.39_merge_165139458 had test failures

Details

Tests

  • Failed: 2 (0.39%)
  • Passed: 505 (99.61%)
  • Other: 0 (0.00%)
  • Total: 507

Annotations

Check failure on line 1512 in Build log

See this annotation in the file changed.

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

Build log #L1512

Script failed with exit code: 1

Check failure on line 1 in Test_NetworkIsolatedCluster_Windows_WithEgress/default

See this annotation in the file changed.

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

Test_NetworkIsolatedCluster_Windows_WithEgress/default

Failed
Raw output
=== RUN   Test_NetworkIsolatedCluster_Windows_WithEgress/default
=== PAUSE Test_NetworkIsolatedCluster_Windows_WithEgress/default
=== CONT  Test_NetworkIsolatedCluster_Windows_WithEgress/default
    test_helpers.go:390: [656.920s] TAGS {Name:Test_NetworkIsolatedCluster_Windows_WithEgress/default ImageName:windows-2025-gen2 OS:windows Arch:amd64 NetworkIsolated:true NonAnonymousACR:true GPU:false WASM:false BootstrapTokenFallback:false KubeletCustomConfig:false Scriptless:false VHDCaching:false MockAzureChinaCloud:false VMSeriesCoverageTest:false}
    test_helpers.go:221: [662.735s] β†’ running scenario...
    test_helpers.go:258: [672.907s] β†’ preparing AKS node...
    vmss.go:476: [683.596s] β†’ creating VMSS wint14n...
    vmss.go:384: [683.602s] VMSS portal link: https://ms.portal.azure.com/#@microsoft.onmicrosoft.com/resource/subscriptions/8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8/resourceGroups/MC_abe2e-westus3_abe2e-azure-bootstrapprofile-cache-v1-a2071_westus3/providers/Microsoft.Compute/virtualMachineScaleSets/wint14n/overview
    vmss.go:390: [683.602s] 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-bootstrapprofile-cache-v1-a2071_westus3/providers/Microsoft.ContainerService/managedClusters/abe2e-azure-bootstrapprofile-cache-v1-a2071/overview
    vmss.go:509: [689.007s] 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: [689.007s] 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-bootstrapprofile-cache-v1-a2071_westus3/providers/Microsoft.Compute/virtualMachineScaleSets/wint14n/virtualMachines/0" --name "abe2e-azure-bootstrapprofile-cache-v1-a2071-bastion" --resource-group MC_abe2e-westus3_abe2e-azure-bootstrapprofile-cache-v1-a2071_westus3 --auth-type ssh-key --username azureuser --ssh-key /tmp/private-key-873429107
        
    bastionssh.go:304: [948.778s] Attempt 1/5 establishing SSH over bastion to 10.224.0.162
    vmss.go:563: [951.172s] VM reached running state
    vmss.go:533: [951.172s] βœ“ creating VMSS wint14n done (267.6s)
    test_helpers.go:461: [951.173s] saved Windows CSE output to scenario-logs/Test_NetworkIsolatedCluster_Windows_WithEgress/default/windows-cse-output.log
    kube.go:152: [951.173s] β†’ waiting for node wint14n to be ready...
    kube.go:174: [951.249s] node wint14n000000 is ready. Taints: null Conditions: [{"type":"MemoryPressure","status":"False","lastHeartbeatTime":"2026-05-21T23:38:38Z","lastTransitionTime":"2026-05-21T23:38:38Z","reason":"KubeletHasSufficientMemory","message":"kubelet has sufficient memory available"},{"type":"DiskPressure","status":"False","lastHeartbeatTime":"2026-05-21T23:38:38Z","lastTransitionTime":"2026-05-21T23:38:38Z","reason":"KubeletHasNoDiskPressure","message":"kubelet has no disk pressure"},{"type":"PIDPressure","status":"False","lastHeartbeatTime":"2026-05-21T23:38:38Z","lastTransitionTime":"2026-05-21T23:38:38Z","reason":"KubeletHasSufficientPID","message":"kubelet has sufficient PID available"},{"type":"Ready","status":"True","lastHeartbeatTime":"2026-05-21T23:38:38Z","lastTransitionTime":"2026-05-21T23:38:38Z","reason":"KubeletReady","message":"kubelet is posting ready status"}]
    kube.go:195: [951.249s] βœ“ waiting for node wint14n to be ready done (0.1s)
    test_helpers.go:343: [951.249s] ⚠️ ##vso[task.logissue type=warning;] Node wint14n took 4m27.576769649s to be created and 76.589036ms to be ready

... [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_NetworkIsolatedCluster_Windows_WithEgress

See this annotation in the file changed.

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

Test_NetworkIsolatedCluster_Windows_WithEgress

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