Open ajchiarello opened 3 years ago
@ajchiarello - Please provide TF manifest to verify this issue at our end.
Here's the BIG-IP resources. In this, I do have a port defined under the virtual_server, because one is required to create the resource; as I said in the original post, changing it to a port list in the F5 and then running anything that triggers a terraform refresh will crash the provider.
resource "bigip_ltm_pool" "consul" {
name = "/K8S/${var.project_name}-pool"
monitors = ["/K8S/https_8501"]
}
resource "bigip_ltm_pool_attachment" "consul_web" {
for_each = local.consul_name_ip_map
pool = bigip_ltm_pool.consul.name
node = "${bigip_ltm_node.consul[each.key].name}:8501"
}
resource "bigip_ltm_node" "consul" {
for_each = local.consul_name_ip_map
name = "/K8S/${each.key}"
address = each.value
}
resource "bigip_ltm_virtual_server" "consul" {
name = "/K8S/${var.project_name}"
destination = var.consul_f5_ip
ip_protocol = "tcp"
port = "8501"
pool = bigip_ltm_pool.consul.name
profiles = ["/Common/tcp"]
source_address_translation = "automap"
}
Created INFRAANO-599 for internal tracking.
I have raised BUG - 1068173, for this issue.
Is there any timeline for resolving this bug?
@ajchiarello - This issue is with another team. We raised this issue BUG - 1068173.
Greetings, is there any updates on this topic or an ETA for a release covering this? We also have some usecases where portlist setup on VS via the TF provider would be required.
@gmouratidis this issue must be resolved in BIGIP to be resolved from ansible. Please followup with BID 1068173
@trinaths How would one go about following up on the bug ID?
I have the same need for port list configuration
Hi @gmouratidis, @ajchiarello and @malacration,
Bug ID 1068173 needs to be fixed first on TMOS. To get an update about this bug ID, you need to open a ticket via https://my.f5.com
Environment
Summary
I've created a virtual_server using the bigip terraform provider. I needed it to use a port list rather than a single port, so I made that change in the GUI, and then ran a terraform plan to see what it would try to change (so I could tell terraform to ignore that change). Instead, the provider crashed when it attempted to refresh the virtual server resource.
Steps To Reproduce
Create a bigip_ltm_virtual_server resource. Go to the web interface and configure the virtual server to use a port list. Run a terraform refresh, plan, or apply.
Output:
Expected Behavior
Ideally, that the terraform provider supported port lists for virtual servers. Minimally, that I can add one in the gui and tell terraform to ignore_changes on it. Minimally, that it doesn't crash the provider completely.