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
I'm receiving the follow error when attempting to apply a Terraform plan with an updated configuration for the dns_lb_pool:
volterra_dns_lb_pool.www-juiceshop-vip: Creating...
│ Error: error creating DnsLbPool: Creating object: Unsuccessful POST at URL https://console.ves.volterra.io/api/public/namespaces/system/dns_lb_pools, status code 409, body {"code":6,"details":[],"message":"Object already exists"}, err %!s(<nil>)
│
│ with volterra_dns_lb_pool.www-juiceshop-vip,
│ on f5xc_dns.tf line 26, in resource "volterra_dns_lb_pool" "www-juiceshop-vip":
│ 26: resource "volterra_dns_lb_pool" "www-juiceshop-vip" {
│
This is a snippet of the plan I'm trying to use:
resource "volterra_dns_lb_pool" "www-juiceshop-vip" {
name = "www-juiceshop-vip"
namespace = "system"
load_balancing_mode = "ROUND_ROBIN"
a_pool {
// One of the arguments from this list "disable_health_check health_check" must be set
disable_health_check = true
max_answers = "1"
health_check {
name = "${volterra_dns_lb_health_check.www-juiceshop-vip-health-check.name}"
}
members {
ip_endpoint = "${aws_eip.WestBIGIPDataEIP.public_ip}"
priority = "10"
ratio = "10"
}
}
use_rrset_ttl = true
}
The pool was created during a previous apply operation, but it appears that the Volterra provider failed to set the object as created and is trying to again create it as a new object.
I'm receiving the follow error when attempting to apply a Terraform plan with an updated configuration for the dns_lb_pool:
This is a snippet of the plan I'm trying to use:
The pool was created during a previous apply operation, but it appears that the Volterra provider failed to set the object as created and is trying to again create it as a new object.
TRACE level terraform.log: https://gist.github.com/grf5/1021e34d18b640a832f4c9ebb61d45d8
The text was updated successfully, but these errors were encountered: