=== RUN   Test_Windows2025Gen2
=== PAUSE Test_Windows2025Gen2
=== CONT  Test_Windows2025Gen2
    azure.go:452: Looking up images in https://ms.portal.azure.com/#@microsoft.onmicrosoft.com/resource/subscriptions/c4c3550e-a965-4993-a50c-628fd38cd3e1/resourceGroups/aksvhdtestbuildrg/providers/Microsoft.Compute/galleries/PackerSigGalleryEastUS/images/aks-windows-2025-gen2/overview
    azure.go:540: Image version /subscriptions/c4c3550e-a965-4993-a50c-628fd38cd3e1/resourceGroups/aksvhdtestbuildrg/providers/Microsoft.Compute/galleries/PackerSigGalleryEastUS/images/windows-2025-gen2/versions/251125.154543.22055 is already in region westus3
    vhd.go:281: got version by tag branch=refs/heads/main: https://ms.portal.azure.com/#@microsoft.onmicrosoft.com/resource/subscriptions/c4c3550e-a965-4993-a50c-628fd38cd3e1/resourceGroups/aksvhdtestbuildrg/providers/Microsoft.Compute/galleries/PackerSigGalleryEastUS/images/aks-windows-2025-gen2/versions//overview
    test_helpers.go:322: TAGS {Name:Test_Windows2025Gen2 ImageName:windows-2025-gen2 OS:windows Arch:amd64 Airgap:false NonAnonymousACR:false GPU:false WASM:false BootstrapTokenFallback:false KubeletCustomConfig:false Scriptless:false VHDCaching:false MockAzureChinaCloud:false}
    vmss.go:173: creating VMSS "winbxo3" with BootstrapConfigMutator/NBC in resource group MC_abe2e-westus3_abe2e-azure-network-v2-fefd8_westus3
    vmss.go:182: 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-v2-fefd8_westus3/providers/Microsoft.Compute/virtualMachineScaleSets/winbxo3/overview
    vmss.go:188: 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-v2-fefd8_westus3/providers/Microsoft.ContainerService/managedClusters/abe2e-azure-network-v2-fefd8/overview
    vmss.go:285: 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:285: SSH Instructions: (may take a few minutes for the VM to be ready for SSH)
        ========================
        kubectl --kubeconfig <(az aks get-credentials --subscription "8ecadfc9-d1a3-4ea4-b844-0d9f87e4d7c8" --resource-group "abe2e-westus3"  --name "abe2e-azure-network-v2-fefd8" -f -) exec -it debug-mariner-tolerated-5ljmn -- bash -c "chroot /proc/1/root /bin/bash -c 'ssh -i sshkey102240255 -o PasswordAuthentication=no -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -o ConnectTimeout=5 [email protected]'"
    vmss.go:330: VM reached running state
    vmss.go:235: created VMSS winbxo3 in resource group MC_abe2e-westus3_abe2e-azure-network-v2-fefd8_westus3
    test_helpers.go:381: saved Windows CSE output to scenario-logs/Test_Windows2025Gen2/windows-cse-output.log
    kube.go:138: waiting for node winbxo3 to be ready in k8s API
    kube.go:174: node winbxo3000000 is ready. Taints: [{"key":"node.cloudprovider.kubernetes.io/uninitialized","value":"true","effect":"NoSchedule"}] Conditions: [{"type":"MemoryPressure","status":"False","lastHeartbeatTime":"2025-12-10T03:50:45Z","lastTransitionTime":"2025-12-10T03:50:45Z","reason":"KubeletHasSufficientMemory","message":"kubelet has sufficient memory available"},{"type":"DiskPressure","status":"False","lastHeartbeatTime":"2025-12-10T03:50:45Z","lastTransitionTime":"2025-12-10T03:50:45Z","reason":"KubeletHasNoDiskPressure","message":"kubelet has no disk pressure"},{"type":"PIDPressure","status":"False","lastHeartbeatTime":"2025-12-10T03:50:45Z","lastTransitionTime":"2025-12-10T03:50:45Z","reason":"KubeletHasSufficientPID","message":"kubelet has sufficient PID available"},{"type":"Ready","status":"True","lastHeartbeatTime":"2025-12-10T03:50:45Z","lastTransitionTime":"2025-12-10T03:50:45Z","reaso