RavinderReddyF5
commented
4 years ago Open RavinderReddyF5 opened 4 years ago
RavinderReddyF5
commented
4 years ago RavinderReddyF5
commented
4 years ago 
@marianne-butaye
I fixed Issue, hope this solves your Problem.
1st time Terraform Apply
root@terraformclient:~/Go_Workspace/src/github.com/terraform-providers/terraform-provider-bigip# terraform apply
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
# bigip_ltm_profile_http2.test-http2 will be created
+ resource "bigip_ltm_profile_http2" "test-http2" {
+ activation_modes = [
+ "alpn",
]
+ concurrent_streams_per_connection = 30
+ connection_idle_timeout = 80
+ defaults_from = "/Common/http2"
+ header_table_size = 3800
+ id = (known after apply)
+ name = "/Common/test-http2"
}
Plan: 1 to add, 0 to change, 0 to destroy.
Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.
Enter a value: yes
bigip_ltm_profile_http2.test-http2: Creating...
bigip_ltm_profile_http2.test-http2: Creation complete after 0s [id=/Common/test-http2]
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.Terraform Show
root@terraformclient:~/Go_Workspace/src/github.com/terraform-providers/terraform-provider-bigip# terraform show
# bigip_ltm_profile_http2.test-http2:
resource "bigip_ltm_profile_http2" "test-http2" {
activation_modes = [
"alpn",
]
concurrent_streams_per_connection = 30
connection_idle_timeout = 80
defaults_from = "/Common/http2"
header_table_size = 3800
id = "/Common/test-http2"
name = "/Common/test-http2"
}2 nd time Terraform apply with Name Change
root@terraformclient:~/Go_Workspace/src/github.com/terraform-providers/terraform-provider-bigip# terraform apply
bigip_ltm_profile_http2.test-http2: Refreshing state... [id=/Common/test-http2]
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
# bigip_ltm_profile_http2.test-http2 will be updated in-place
~ resource "bigip_ltm_profile_http2" "test-http2" {
activation_modes = [
"alpn",
]
concurrent_streams_per_connection = 30
connection_idle_timeout = 80
defaults_from = "/Common/http2"
header_table_size = 3800
id = "/Common/test-http2"
~ name = "/Common/test-http2" -> "/Common/test-http2-new"
}
Plan: 0 to add, 1 to change, 0 to destroy.
Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.
Enter a value: yes
bigip_ltm_profile_http2.test-http2: Modifying... [id=/Common/test-http2]
bigip_ltm_profile_http2.test-http2: Modifications complete after 0s [id=/Common/test-http2]
Apply complete! Resources: 0 added, 1 changed, 0 destroyed.
Note: this Will not Change Profile Name on BIG-IP
RavinderReddyF5
commented
4 years ago 
I know that the 'name' cannot be updated on the F5 device (I usually use lifecycle's ignore_change on both 'name' and 'partition' to remedy to that); but this comportment is different than other resources in this case.
When I change the 'name' of the resource (without lifecycle use), other resources succeed the apply phase even when the F5 device cannot change this property; but the 'bigip_ltm_profile_http2' resource produces a Terraform Crash.
Below are the steps to reproduce this error: 1st terraform apply
2nd terraform apply & CRASH
Here is my Terraform version info:
The crash also causes the loss of the state regarding this resource (marked as not created yet after crash even though is still exists on the F5 device).