0

Failed to install Aviatrix Cloud Controller at AWS using Sandbox Starter Tool

I was trying to spin up an Aviatrix Cloud Controller at AWS using Sandbox Starter Tool, but keep getting these errors:

> The controller will be launched in us-east-1. Initializing modules... Initializing the backend... Initializing provider plugins... - Checking for available provider plugins... --> Controller launch failed, aborting.
Registry service unreachable. This may indicate a network issue, or an issue with the requested Terraform Registry. Registry service unreachable. This may indicate a network issue, or an issue with the requested Terraform Registry.
registry service is unreachable >

If anyone has faced the same issue before, kindly help me to find a solution. I ran starter Tool as docker container in my laptop and accessing to Hashicorp registry is fine from my laptop, not sure why it complains Terraform registry service is unreachable.

===Debug Message==

--> Controller SSH key already exists, skipping. --> OK. --> Now going to launch the controller. The public IP of the controller will be shared with Aviatrix for tracking purposes. --> The controller will be launched in us-east-1. Initializing modules... Initializing the backend... Initializing provider plugins... - Checking for available provider plugins... --> Controller launch failed, aborting.
Registry service unreachable. This may indicate a network issue, or an issue with the requested Terraform Registry. Registry service unreachable. This may indicate a network issue, or an issue with the requested Terraform Registry.
registry service is unreachable, check https://status.hashicorp.com/ for status updates
registry service is unreachable, check https://status.hashicorp.com/ for status updates
Could not satisfy plugin requirements Plugin reinitialization required. Please run "terraform init". Plugins are external binaries that Terraform uses to access and manipulate resources. The configuration provided requires plugins which can't be located, don't satisfy the version constraints, or are otherwise incompatible. Terraform automatically discovers provider requirements from your configuration, including providers used in child modules. To see the requirements and constraints from each module, run "terraform providers".
provider.aws: no suitable version installed version requirements: "(any version)" versions installed: none
provider.http: no suitable version installed version requirements: "(any version)" versions installed: none --> Controller launch failed, aborting.

6replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • I've been able to recreate your issue by denying access to the Internet from the container. Since you mention that you're able to access from the host machine. I'm wondering if there's something else involved - custom docker networking or a corporate network that detects and blocks traffic from workstation-hosted VMs or containers. I'd be interested what the response is if you 'docker exec' into the container and run curl to the terraform registry:
    docker exec -it <container_id> /bin/sh
    curl https://registry.terraform.io

    Like
    • John Smoker thank you John, I will give a try and update here, thanks for your response!

      Like
  • John Smoker  Hi John, here is the exec result ..

    C:\Users\zhengquann>docker exec -it c11303be7494 /bin/bash
    bash-5.0# curl https://registry.terraform.io
    curl: (60) SSL certificate problem: certificate is not yet valid
    More details here: https://curl.haxx.se/docs/sslcerts.html

    curl failed to verify the legitimacy of the server and therefore could not
    establish a secure connection to it. To learn more about this situation and
    how to fix it, please visit the web page mentioned above.
    bash-5.0#

    What do you suggest to check further?

    Like
      • John Smoker
      • Customer Solutions Architect
      • John_Smoker
      • yesterday
      • Reported - view

      Ni Zhengquan That looks like the clock on the machine that is hosting the container may be out of sync.

      Like
    • John Smoker  Hi John, managed to solve the time sync problem by rebooting laptop, however when came to deploy Aviatrix Transit in AWS, hit another issue. is it because Terraform version mis-match?

       

      Initializing the backend... Initializing provider plugins... - Checking for available provider plugins... - Downloading plugin for provider "aviatrix" (terraform-providers/aviatrix) 2.16.3... Warning: registry.terraform.io: For users on Terraform 0.13 or greater, this provider has moved to AviatrixSystems/aviatrix. Please update your source in required_providers.
      Error verifying checksum for provider "aws" The checksum for provider distribution from the Terraform Registry did not match the source. This may mean that the distributed files were changed after this version was released to the Registry.
      unable to verify checksum
      Could not satisfy plugin requirements Plugin reinitialization required. Please run "terraform init". Plugins are external binaries that Terraform uses to access and manipulate resources. The configuration provided requires plugins which can't be located, don't satisfy the version constraints, or are otherwise incompatible. Terraform automatically discovers provider requirements from your configuration, including providers used in child modules. To see the requirements and constraints from each module, run "terraform providers".
      provider.aviatrix: new or changed plugin executable
      provider.aws: no suitable version installed version requirements: "(any version)" versions installed: none --> Failed to launch AWS transit, aborting.

      Like
  • Hi, I have a similar but not exact issue...

     

    Been trying for hours to get the sandbox environment going... I've followed all the prerequisites and changed my AWS keys multiple times but no luck...

    This is the error from the debug window.

     

    Initializing modules... Initializing the backend... Initializing provider plugins... The following providers do not have any version constraints in configuration, so the latest version was installed. To prevent automatic upgrades to new major versions that may contain breaking changes, it is recommended to add version = "..." constraints to the corresponding provider blocks in configuration, with the constraint strings suggested below. * provider.aws: version = "~> 3.36" * provider.http: version = "~> 2.1" Terraform has been successfully initialized! You may now begin working with Terraform. Try running "terraform plan" to see any changes that are required for your infrastructure. All Terraform commands should now work. If you ever set or change modules or backend configuration for Terraform, rerun this command to reinitialize your working directory. If you forget, other commands will detect it and remind you to do so if necessary. module.avtx_iam_role.data.http.iam_policy_ec2_role: Refreshing state... module.avtx_iam_role.data.http.iam_policy_assume_role: Refreshing state... module.avtx_controller_instance.data.http.avx_iam_id: Refreshing state... --> Controller launch failed, aborting.

    error configuring Terraform AWS Provider: error validating provider credentials: error calling sts:GetCallerIdentity: InvalidClientTokenId: The security token included in the request is invalid. status code: 403, request id: 18790cfb-1632-45a7-8533-dae3508fe40d on main.tf line 3, in provider "aws": 3: provider "aws" { --> Controller launch failed, aborting.

    Please help!

    Like
Like Follow
  • 7 hrs agoLast active
  • 6Replies
  • 13Views
  • 3 Following