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
grid_network.net1: Modifying... [id=94446cd5-cafc-4847-970d-2d4cd3283cf0]
grid_network.net1: Still modifying... [id=94446cd5-cafc-4847-970d-2d4cd3283cf0, 10s elapsed]
grid_network.net1: Still modifying... [id=94446cd5-cafc-4847-970d-2d4cd3283cf0, 20s elapsed]
grid_network.net1: Still modifying... [id=94446cd5-cafc-4847-970d-2d4cd3283cf0, 30s elapsed]
grid_network.net1: Still modifying... [id=94446cd5-cafc-4847-970d-2d4cd3283cf0, 40s elapsed]
grid_network.net1: Still modifying... [id=94446cd5-cafc-4847-970d-2d4cd3283cf0, 50s elapsed]
grid_network.net1: Still modifying... [id=94446cd5-cafc-4847-970d-2d4cd3283cf0, 1m0s elapsed]
grid_network.net1: Modifications complete after 1m7s [id=94446cd5-cafc-4847-970d-2d4cd3283cf0]
╷
│ Error: Provider produced inconsistent final plan
│
│ When expanding the plan for grid_deployment.d4 to include new values learned so far during apply, provider "registry.terraform.io/threefoldtech/grid" produced an invalid new value for .ip_range: was cty.StringVal(""), but now cty.StringVal("10.30.7.0/24").
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
Trying a second time always works.
Steps to Reproduce
deploy a vm with network
add a second vm to the existing deployment
Extra info
First deployment works, error comes up consistently when adding to the deployment.
Deploy one vm with internal network -> works
Deploy second vm within the same deployment (so extending the main.tf) -> above error
Doing an apply again after the error makes the deployment work the second time. This behavior (terraform apply again after the error) is also consistent.
The text was updated successfully, but these errors were encountered:
Yeah, this limitation is documented here, but it looks like terraform supports updating the computed value during planning if the to-be-known value is known at planning time hashicorp/terraform-plugin-sdk#818 (comment)
Had the error again while expanding from a 2 to a 3 vm deployment
grid_network.net1: Modifying... [id=20778380-9ce2-4231-9992-840b352c5300]
grid_network.net1: Still modifying... [id=20778380-9ce2-4231-9992-840b352c5300, 10s elapsed]
grid_network.net1: Still modifying... [id=20778380-9ce2-4231-9992-840b352c5300, 20s elapsed]
grid_network.net1: Still modifying... [id=20778380-9ce2-4231-9992-840b352c5300, 30s elapsed]
grid_network.net1: Still modifying... [id=20778380-9ce2-4231-9992-840b352c5300, 40s elapsed]
grid_network.net1: Still modifying... [id=20778380-9ce2-4231-9992-840b352c5300, 50s elapsed]
grid_network.net1: Modifications complete after 50s [id=20778380-9ce2-4231-9992-840b352c5300]
╷
│ Error: Provider produced inconsistent final plan
│
│ When expanding the plan for grid_deployment.d3 to include new values learned so far during apply, provider "registry.terraform.io/threefoldtech/grid" produced an invalid new value for .ip_range: was
│ cty.StringVal(""), but now cty.StringVal("10.41.5.0/24").
Terraform Version
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
Actual Behavior
This error:
Trying a second time always works.
Steps to Reproduce
Extra info
First deployment works, error comes up consistently when adding to the deployment.
The text was updated successfully, but these errors were encountered: