Hello,
All of our VMs recently spawned seems to ignore our custom domain settings. Older VMs in the same VMSS seems to work just fine.
After investigation, it looks like the newer VMs use a new azure-cli version which is incompatible with some commands inside the startVMSS.ps1 script.
This is quite a pressing issue as we can’t deploy with custom domains anymore !
One command causing issue is at line 142 in startVMSS.ps1
az vmss nic list --vmss-name $vmssName -g $resourceGroup --query "[].ipConfigurations[?privateIpAddress=='$privateIpAddress'].[publicIpAddress.id][0][0]" | ConvertFrom-Json where the publicIpAddress got renamed publicIPAddress in newer version of azure-cli.
The breaking changes seems to have come with azure-cli 2.46.0.
It is worth noting that the workaround we are planning is gonna be unnecessary complicated, mainly because:
- We can’t easily update those azure scripts. It would be very convenient to be able to use custom scripts the same way we can provide custom servers.
- ‘Use a custom image’ don’t seems to work, or at least we and other people on this forum haven’t been able to use it.