Closed mimckitt closed 1 month ago
We have fixed the CLI bug. Any update on when we could get this PS bug addressed?
https://github.com/Azure/azure-cli/pull/29234
CC @Sandido
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @TravisCragg-MSFT, @sandeepraichura.
@mimckitt Thanks for creating this issue. We discussed further steps offline and will handle this internally.
Description
Creating a scale set with flexible orchestration does not honor the upgrade policy set. For example,
New-AzVmss -ResourceGroupName "myResourceGroup" -Location "EastUS" -VMScaleSetName "myScaleSet" -OrchestrationMode "Flexible" -VirtualNetworkName "myVnet" -SubnetName "mySubnet" -PublicIpAddressName "myPublicIPAddress" -LoadBalancerName "myLoadBalancer" -UpgradePolicyMode "Automatic"
This command successfully creates the scale set, but the upgrade policy is still manual:
Automatic upgrade policy recently became available for flexible orchestration. Also seeing this issue for Azure CLI: https://github.com/Azure/azure-cli/issues/29191
updating an existing scale set to automatic works fine
$vmss = Get-AzVmss -ResourceGroupName "myResourceGroup" -VMScaleSetName "myScaleSet"
Update-Azvmss -ResourceGroupName "myResourceGroup" -Name "myScaleSet" -UpgradePolicyMode "Automatic" -VirtualMachineScaleSet $vmss
Issue script & Debug output
Environment data
Module versions
Error output