You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The VM size 'Standard_D2als_v6' cannot boot with OS image or disk. Please check that disk controller types supported by the OS image or disk is one of the supported disk controller types for the VM size 'Standard_D2als_v6'
VM storage controller type seems to be NVMe, but the OS image being used (AKSUbuntu?) probably isn't marked as supporting NVMe.
This is happening by default with an AKS NAP cluster. Right out of the box. It's been an hour now and it keeps repeating the same, so I'm not sure it will ever get past it.
Expected Behavior
Works out of the box?
Actual Behavior
Does not.
Steps to Reproduce the Problem
az aks create --name testtest --resource-group testtest --node-provisioning-mode Auto --network-plugin azure --network-plugin-mode overlay --network-dataplane cilium --debug --nodepool-taints CriticalAddonsOnly=true:NoSchedule --verbose -l eastus
Resource Specs and Logs
Not sure what this would entail.
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The text was updated successfully, but these errors were encountered:
Version
The VM size 'Standard_D2als_v6' cannot boot with OS image or disk. Please check that disk controller types supported by the OS image or disk is one of the supported disk controller types for the VM size 'Standard_D2als_v6'
VM storage controller type seems to be NVMe, but the OS image being used (AKSUbuntu?) probably isn't marked as supporting NVMe.
This is happening by default with an AKS NAP cluster. Right out of the box. It's been an hour now and it keeps repeating the same, so I'm not sure it will ever get past it.
Expected Behavior
Works out of the box?
Actual Behavior
Does not.
Steps to Reproduce the Problem
az aks create --name testtest --resource-group testtest --node-provisioning-mode Auto --network-plugin azure --network-plugin-mode overlay --network-dataplane cilium --debug --nodepool-taints CriticalAddonsOnly=true:NoSchedule --verbose -l eastus
Resource Specs and Logs
Not sure what this would entail.
Community Note
The text was updated successfully, but these errors were encountered: