Closed yuxisun1217 closed 1 year ago
Compute
What is the current status of this ticket? This also isn't a feature request, it's a bug report.
There is an open issue with RedHat related to this and I'd like to close it out or at least give them a status update.
Hello, can you share the debug log?
I don't think there is a debug log but there are repro instrunctions if you want to try it yourself.
Create a NIC with accelerated-networking enabled Use "az vm create --size Standard_ND6s" to create a VM with this NIC attached. The step2 VM can be created successfully. But it should not success because this VM size doesn't support AN Use "az vm create --size Standard_NV6" to create a VM with an AN enabled NIC attached The step4 is failed because NV6 doesn't support AN. And from the output message we can see that ND and NCv3 series are in "Compatible VM sizes" which is incorrect.
Our test subscription doesn't have quota to create ND or NCv3 vms. But query vm SKUs that support accelerated network by this CLI command,
az vm list-skus --location eastus --all true --resource-type virtualMachines --query '[].{size:size, name:name, acceleratedNetworkingEnabled: capabilities[?name==`AcceleratedNetworkingEnabled`].value | [0]}' --output table
And the output shows that Standard_ND6s and Standard_NC6s_v3 does support AN, and Standard_NV6 doesn't.
That is exactly the problem. https://docs.microsoft.com/en-us/azure/virtual-machines/nd-series ND series v1 doesn't support AN. It's a bug that they're showing up as supporting it.
Thank you for your feedback. This has been routed to the support team for assistance.
Removing the CXP Attention label after discussing with @yonzhan
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Drewm3, @avirishuv, @vaibhav-agar, @amjads1.
Author: | yuxisun1217 |
---|---|
Assignees: | zhoxing-ms, cxznmhdcxz |
Labels: | `Compute`, `Service Attention`, `customer-reported`, `feature-request` |
Milestone: | Backlog |
@avirishuv can you please take a look at this issue?
Travis will update this issue shortly. It appears that we have a typo in the config data for these VM sizes in the VM SKU API. At least some of these VM sizes do not actually support AN, but they are listed in the API as supporting AN. Configuring AN should not cause a failure on these sizes, but the networking will not be accelerated. We are investigating how we can fix this without causing failures because if we remove AN support from the SKU API, then it could break existing scripts that would start failing once AN support is removed because it would now cause the VM deployments to fail instead of the deployment being successful with slower networking.
@TravisCragg-MSFT Do you have an update on this item?
I have updated the docs to show this case. We are going to continue to allow these sizes to use the flag so that it will not impact existing VMs, but AN will NOT be enabled.
I am closing this issue, please @me with a reply if anything further is needed.
Describe the bug When I try to create a VM that the size doesn't support accelerated-networking, it should report an error message and stop creating, but for the ND and NCv3 sizes they are created successfully. And the message also shows that ND and NCv3 series supports accelerated-networking. I'm not quite sure if this is an issue of azure-cli. It looks more like an issue of some Azure database. Could you please help to figure out where to open this issue? Thanks!
To Reproduce
Additional context