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
1 error(s) occurred:
* azurerm_route_table.primary: 1 error(s) occurred:
* azurerm_route_table.primary: Error Creating/Updating Route Table "primary" (Resource Group "Network-Routes"): network.RouteTablesClient#CreateOrUpdate: Failure sending request: StatusCode=400 -- Original Error: Code="NextHopIpAddressNotAllowed" Message="NextHopIpAddress 192.168.0.1 for route UDR_BlackHole cannot be specified. This field can only be specified for NextHopType VirtualAppliance." Details=[]
Steps to Reproduce
terraform apply the "before" config
terraform apply the "after" config
Important Factoids
References
The text was updated successfully, but these errors were encountered:
Ran into this same issue, but with the routes itself. There the issue isn't as apparent, as changing the name creates a new resource, but if the name stays the same, it doesn't work.
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 6, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Before
After
Expected Behavior
Route is updated
Actual Behavior
Steps to Reproduce
terraform apply
the "before" configterraform apply
the "after" configImportant Factoids
References
The text was updated successfully, but these errors were encountered: