Open nickzxcv opened 1 year ago
I also tried setting seller_region = var.region instead of getting the region name from the interconnect, and this came up with a different error:
equinix_ecx_l2_connection.gcpi-dot1q: Creating...
╷
│ Error: Equinix REST API error: Message: "Bad Request", HTTPCode: 400, ApplicationErrors: [Code: "IC-LAYER2-AUTH-004", Property: "authorizationKey", Message: "Authentication key pattern did not match regex specification", AdditionalInfo: "Pairing key must end with /1"]
│
│ with equinix_ecx_l2_connection.gcpi-dot1q,
│ on main.tf line 62, in resource "equinix_ecx_l2_connection" "gcpi-dot1q":
│ 62: resource "equinix_ecx_l2_connection" "gcpi-dot1q" {
│
╵
The "Pairing key must end with /1" problem was the same as https://github.com/equinix/terraform-provider-equinix/issues/36 and solved like this:
#availability_domain_1 = "iad-zone1-1"
#availability_domain_2 = "iad-zone2-1"
availability_domain_1 = "availability-domain-1"
availability_domain_2 = "availability-domain-2"
Still has the problem with the region name though.
@nickzxcv Upon looking at the error message, the vlan attachement key is invalid. Could you please check the pairing key format, here is the sample key "946h29b6-8649-4d45-9a08-0f1f4a7cd7ab/us-west1/1"
@anchala71 I solved the key issue with the information from https://github.com/equinix/terraform-provider-equinix/issues/36 (I asked Google separately about that, why the zone names used with Equinix are not according to https://cloud.google.com/network-connectivity/docs/interconnect/concepts/choosing-colocation-facilities ) but the "inconsistent final plan" issue for the region name is still maybe a problem.
Community Note
Terraform Version
Terraform v1.5.0 on linux_amd64
Affected Resource(s)
equinix_ecx_l2_connection
Terraform Configuration Files
main.tf:
Debug Output
https://gist.github.com/nickzxcv/2e1678a6b575729efe59e2fa469b29b1
Expected Behavior
Create the equinix_ecx_l2_connection
Actual Behavior
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
google_compute_network.asdf: Creating... google_compute_network.asdf: Still creating... [10s elapsed] google_compute_network.asdf: Still creating... [20s elapsed] google_compute_network.asdf: Creation complete after 22s [id=projects/infra-258014/global/networks/asdf-network-1] google_compute_router.asdf: Creating... google_compute_router.asdf: Still creating... [10s elapsed] google_compute_router.asdf: Still creating... [20s elapsed] google_compute_router.asdf: Creation complete after 21s [id=projects/infra-258014/regions/us-east4/routers/asdf-router-1] google_compute_interconnect_attachment.asdf: Creating... google_compute_interconnect_attachment.asdf: Still creating... [10s elapsed] google_compute_interconnect_attachment.asdf: Creation complete after 12s [id=projects/infra-258014/regions/us-east4/interconnectAttachments/asdf] ╷ │ Error: Provider produced inconsistent final plan │ │ When expanding the plan for equinix_ecx_l2_connection.gcpi-dot1q to include new values learned so far during apply, provider "registry.terraform.io/equinix/equinix" produced an invalid new value for │ .seller_region: was cty.StringVal("us-east4"), but now cty.StringVal("https://www.googleapis.com/compute/v1/projects/infra-258014/regions/us-east4"). │ │ This is a bug in the provider, which should be reported in the provider's own issue tracker. ╵
Steps to Reproduce
terraform apply