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
compute.VirtualMachineScaleSetsClient#CreateOrUpdate: Failure sending request: StatusCode=409 -- Original Error: failed request: autorest/azure: Service returned an error. Status=<nil> Code="PropertyChangeNotAllowed" Message="Changing property 'linuxConfiguration.ssh.publicKeys' is not allowed."
Steps to Reproduce
Create test-vmss through the portal. (This created a resource group with a vnet, public ip, load balancer, and the vm scale set.)
Import this resource into terraform by creating a resource file and importing state with terraform import.
Run terraform apply
Important Factoids
The key difference is that, when the portal creates VMSS resources, I creates them with a null ssh property.
When terraform applies its changes, it tries to set this value to an empty public keys list.
These two settings mean the same thing, however; the azure api does not allow you to change the null value once it has been deployed, and since terraform always tries to post the ssh.publicKeys array, it will never succeed until this resource is re-created via terraform.
This is confirmed with Microsoft to be issue with the version of the compute api that is built into this provider. 2017-03-30 fails because it does not allow modifications to the ssh object. 2017-12-01 succeeds because it does allow this modification.
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 👉 [email protected]. 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.
Terraform Version
Terraform version: 0.11.3 3802b14260603f90c7a1faf55994dcc8933e2069
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
Deployment of VM scale set should succeed
Actual Behavior
Got unexpected error
Steps to Reproduce
test-vmss
through the portal. (This created a resource group with a vnet, public ip, load balancer, and the vm scale set.)terraform apply
Important Factoids
null
ssh property.When terraform applies its changes, it tries to set this value to an empty public keys list.
These two settings mean the same thing, however; the azure api does not allow you to change the null value once it has been deployed, and since terraform always tries to post the ssh.publicKeys array, it will never succeed until this resource is re-created via terraform.
ssh
object. 2017-12-01 succeeds because it does allow this modification.References
The text was updated successfully, but these errors were encountered: