f5devcentral / terraform-xc-aws-ce

Terraform to create F5XC AWS cloud CE
Apache License 2.0
4 stars 4 forks source link

Getting multiple 400 errors when using manual mode to deploy CE's in aws #6

Closed Nettas closed 5 months ago

Nettas commented 6 months ago

Getting multiple 400 errors when using manual mode to deploy CE's in aws. Using https://github.com/f5devcentral/terraform-xc-aws-ce/tree/main and trying to deploy the three_node_cluster_multi_nic_new_vpc_new_subnet option:

Error outputs: Error: error creating SecuremeshSite: Creating object: Unsuccessful POST at URL https://visa.console.ves.volterra.io/api/public/namespaces/system/securemesh_sites, status code 400, body <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd> │ │ │ │ │ │ We're sorry... │ │ │ │ │

│ │
│ error │

Invalid parameter: redirect_uri

│ │ <a id="backToApplication" │ href="#" │ class="btn btn-primary btn-block btn-lg"> │ Try again │ │
│ │ │

│ │ │ │ │ with module.f5xc_aws_cloud_ce_three_node_multi_nic_new_vpc_new_subnet.module.secure_mesh_site[0].volterra_securemesh_site.secure_mesh_site, │ on ../../modules/f5xc/secure-mesh-site/main.tf line 1, in resource "volterra_securemesh_site" "secure_mesh_site": │ 1: resource "volterra_securemesh_site" "secure_mesh_site" { │ ╵ ╷ │ Error: error creating Token: Creating object: Unsuccessful POST at URL https://visa.console.ves.volterra.io/api/public/namespaces/system/tokens, status code 400, body <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd> │ │ │ │ │ │ We're sorry... │ │ │ │ │
│ │
│ error │

Invalid parameter: redirect_uri

│ │ <a id="backToApplication" │ href="#" │ class="btn btn-primary btn-block btn-lg"> │ Try again │ │
│ │ │

│ │ │ │ │ with module.f5xc_aws_cloud_ce_three_node_multi_nic_new_vpc_new_subnet.volterra_token.site, │ on ../../modules/f5xc/ce/aws/main.tf line 1, in resource "volterra_token" "site": │ 1: resource "volterra_token" "site" {

cklewar commented 5 months ago

seems to be related to HTTP redirect and not a TF issue.