Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot mix Accelerated Networking and Non-Accelerated Networking VMs in the same availability set. #782

Closed
jzampieron opened this issue Feb 1, 2018 · 3 comments
Assignees
Milestone

Comments

@jzampieron
Copy link
Contributor

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.

@tombuildsstuff
Copy link
Contributor

hey @jzampieron

Thanks for opening this issue :)

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

Thanks!

@tombuildsstuff
Copy link
Contributor

Fixed via #852

@ghost
Copy link

ghost commented Mar 31, 2020

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 ghost locked and limited conversation to collaborators Mar 31, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants