AWS new vpcid length of 17 makes bootstrap fail

[Chris Scheper]

When bootstrapping to a newly created vpc with 17 character length bootstrap fails with:
Error details: The vpc ID 'vpc-1234567890abcdef0' does not exist (InvalidVpcID.NotFound)

Juju 2.4
Worked last week, doesn't work with new 17 character length vpcid this week
Validated vpc id multiple times, attempted bootstrap in new vpcs created in 3 regions with same error.

[John A Meinel (jameinel)]

I just went through the EC2 pages to upgrade our account to allow long VPC ids, and created a VPC that has the new 17 character tail: "vpc-05e7d3381d4fa7617"
'juju bootstrap aws/eu-west-1 --model-defaults vpc-id=vpc-05e7d3381d4fa7617"
worked as expected.

I wonder if you are bootstrapping into a different region? If you just do:
"juju bootstrap aws" then it will create instances in us-east-1, IIRC, and VPC are restricted to a single region.

[Chris Scheper (chris.scheper)]

John,

  In order to recreate the full command I used to bootstrap, I recreated everything including the network vpc and subnets from the ground up for the 4th time today using this...

  `juju bootstrap --config vpc-id=vpc-1234567890abcdefg --config vpc-id-force=true --credential=my-aws-cred aws/us-east-1 my_controller_name --to subnet=172.32.56.0/24 --debug`

  Due to network security requirements we are unable to boot our controller in the default public subnet created by AWS. Thus requiring the vpc-id-force option and configuring the controller to instantiate itself into a non-default subnet.

  Luckily this 4th attempt worked. However that does leave us wondering where the problem was. Could have been on the AWS side for some reason. But I'm ok closing this if you would prefer. It is working now.

Thanks,
-Chris

[Launchpad Janitor (janitor)]

[Expired for juju because there has been no activity for 60 days.]