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
This is actually an undocumented (at least per the published Microsoft Azure Rest API for VM availability sets) behavior of the Azure REST API.
If you try to create a VM with Accelerated Networking in an availability set with an existing VM which does not already use AN, then the API throws an error.
* azurerm_virtual_machine.machinename: compute.VirtualMachinesClient#CreateOrUpdate: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="ExistingAvailabilitySetWasNotDeployedOnAcceleratedNetworkingEnabledCluster" Message="Cannot add Virtual Machine with accelerated networking-enabled nics (/subscriptions/xxx/resourceGroups/xxx/providers/Microsoft.Compute/virtualMachines/databaseNodeU0) on an existing non-accelerated networking AvailabilitySet (/subscriptions/xxx/resourceGroups/xxx/providers/Microsoft.Compute/availabilitySets/databaseVmAvailSet)." Details=[]
Terraform Version
v0.11.1
Affected Resource(s)
Please list the resources as a list, for example:
azurerm_virtual_machine
azurerm_network_interface
Important Factoids
This ticket is for reference only. It is not likely something that can be fixed in the provider. At least not yet.
The text was updated successfully, but these errors were encountered:
Based on the exception message being returned ExistingAvailabilitySetWasNotDeployedOnAcceleratedNetworkingEnabledCluster - it appears this should be possible providing the Availability Set is deployed on a cluster which supports Accelerated Networking. It's possible to achieve this either by recreating the Availability Set (as you've seen) or (from memory) by shutting down all machines in the Availability Set and then starting them again. I've opened PR #852 which includes some documentation updates to mention this
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks!
ghost
locked and limited conversation to collaborators
Mar 31, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This is actually an undocumented (at least per the published Microsoft Azure Rest API for VM availability sets) behavior of the Azure REST API.
If you try to create a VM with Accelerated Networking in an availability set with an existing VM which does not already use AN, then the API throws an error.
Terraform Version
v0.11.1
Affected Resource(s)
Please list the resources as a list, for example:
Important Factoids
This ticket is for reference only. It is not likely something that can be fixed in the provider. At least not yet.
The text was updated successfully, but these errors were encountered: