Closed ptrautberg closed 2 months ago
Thank you for opening this issue, we will look into it.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @dyu1208, @FumingZhang, @andyliuliming.
@ptrautberg this is a server-side issue, and creating a support ticket (e.g., via Azure Portal) is a better way to handle issues like this.
I checked the code and found that this was a problem caused by a validation on the server side. It has been fixed and is being deployed. You could use this page to track the release progress of AKS. Once the fix (included in version v20240716) is deployed to the region where your cluster is located (it will take about 1 week if nothing unexpected happens), you could retry the command (no matter via azure-cli or terraform), and it should work. https://releases.aks.azure.com/webpage/index.html
Or, if you want a workaround immediately, please reach out to the support team, thanks!
@FumingZhang, thanks for that. Now I see in release 2024-07-16 information that OS SKU migration is GA starting from this release - my mistake, I didn't check that.
Describe the bug
According to docs we can now perform an in-place upgrade of node's OS - directly from CLI or via IaC. When I'm trying to use this feature and migrate from Ubuntu to Azure Linux, I'm getting
Changing property 'agentPoolProfile.OSSKU' is not allowed
error.The same issue is opened for Terraform's AzureRM provider - link.
Related command
az aks nodepool update --resource-group <rg> --cluster-name <aks> --name <nodepool> --os-sku AzureLinux
Errors
Issue script & Debug output
Expected behavior
Migrate OS to Azure Linux
Environment Summary
Additional context
Update using aks-preview extension also didn't work.