Solved

Sandbox Starter - controller launch failed

G
Badge

Hello all,


 


I am trying to deploy the SST through the AMI, however, the procedure fails with the following debug outcome. Any clue on how fixing it, please?


 


An error occurred (NoSuchEntity) when calling the GetRole operation: The role with name aviatrix-role-ec2 cannot be found. ╷ │
Error launching source instance: InvalidBlockDeviceMapping: Volume of size 32GB is smaller than snapshot 'snap-0510ea2db4fff68ce', expect size >= 64GB │ status code: 400, request id: 4df59532-76fe-4f8c-8773-badac9d2c17b │ │ with module.avtx_controller_instance.aws_instance.aviatrixcontroller[0], │ on aviatrix-controller-build/main.tf line 22, in resource "aws_instance" "aviatrixcontroller": │ 22: resource "aws_instance" "aviatrixcontroller" { │ ╵ --> Controller launch failed, aborting.

icon

Best answer by John_Smoker 20 May 2022, 03:18

View original

11 replies

Dariusz_Terefenko
Badge

Do the basic steps first:


1) make sure that role exists with policies and that you have KP in the the us-east-1 region


2) check the main.tf or variables.tf for size attribute in resource or as input via vars as it has to be minimum 64GB to fit the snapshot


You can reference this article as it actually gives well explained steps:


https://community.aviatrix.com/t/g9hx9jh#launch-sandbox-starter-aws-ec2-instance


GL!

John_Smoker
Userlevel 2
Badge +1

Giuseppe Amendolara We released a new controller ami that exposed a bug in v1.1.6, resulting in the error you posted. Version 1.1.7 has just been released to address this. You'll need to:



  • From within the sst ui, click on 'Destroy' in the top-right corner to remove any deployed artifacts from your initial attempt (if you haven't already).

  • Terminate the sst instance that you launched from ami.

  • Launch a new sst ami (which will pull in the latest version - 1.1.7)


Appreciate you reporting this issue. Hope this helps.

S

Your startup guide here https://docs.aviatrix.com/StartUpGuides/aviatrix-cloud-controller-startup-guide.html#id1


It pulls up CF for BYOL and template at https://aviatrix-cloudformation-templates.s3-us-west-2.amazonaws.com/avx-awsmp-BYOL.template


When using this template I see the same error


Volume of size 32GB is smaller than snapshot 'snap-0e1fb5b23d1e8e214', expect size >= 64GB (Service: AmazonEC2; Status Code: 400; Error Code: InvalidBlockDeviceMapping; Request ID: 1a53edfe-2792-4922-85f7-1a694672824c; Proxy: null)


 


Is there an updated template to use?

John_Smoker
Userlevel 2
Badge +1

Shaye F It seems the template has been changed to 64 if you haven't already noticed the update.

G
Badge


John Smoker
The template is now working perfectly. Thanks for the heads-up!
 


Z

I'm using sandbox starter 1.4.1 and I keep getting an error at Aviatrix Transit in AWS.  I tried these steps and it still gives an error.



  • From within the sst ui, click on 'Destroy' in the top-right corner to remove any deployed artifacts from your initial attempt (if you haven't already).

  • Terminate the sst instance that you launched from ami.

  • Launch a new sst ami (which will pull in the latest version - 1.1.7)

John_Smoker
Userlevel 2
Badge +1

zhill8282 What's the error you're getting?

Z

John Smoker It just says "error you can see details in debug" but there's nothing to click to see the debug.

John_Smoker
Userlevel 2
Badge +1

zhill8282 In the bottom-right corner, there is a blue "bug" icon. This will open a side panel with the most recent logging text

Z

John Smoker controller version validation failed: current Terraform branch does not support controller version: UserConnect-7.0. Please go to 'https://registry.terraform.io/providers/AviatrixSystems/aviatrix/latest/docs/guides/release-compatibility' for version construct instructions │ │ with provider["registry.terraform.io/aviatrixsystems/aviatrix"], │ on aviatrix_aws.tf line 1, in provider "aviatrix": │ 1: provider "aviatrix" {} │ ╵ --> Failed to launch AWS transit, aborting.

Z

this is my version UserConnect-7.0.1373

Reply


Terms & Conditions