bootstrap not respecting subnet assignment

[james beedy]

$ juju --version
2.8-rc3-focal-amd64

juju bootstrap aws/us-west-2 ovs-aws-us-west-2 --credential james-ovs --to subnet=subnet-0f882bf41d65b52c9

A bootstrap instance spawns in a subnet that is not subnet-0f882bf41d65b52c9.

Let me know if there is anything else I can provide.

thanks

[Simon Richardson (simonrichardson)]

I believe this is fixed in the following PR https://github.com/juju/juju/pull/11684

[james beedy (jamesbeedy)]

@manadart

debug bootstrap output - https://paste.ubuntu.com/p/yzdsMN6Pdy/

[Joseph Phillips (manadart)]

What is the CIDR for subnet-0e8e64503b2a37e08?

172.31.30.171 is definitely not in it?

I've tried more ways to reproduce this. It succeeds whenever I see log output like yours.

- When I specify a region that the subnet is not in, I get an error as expected.
- When I specify a subnet ID from a VPC other than the default, I also get an error.

[james beedy (jamesbeedy)]

@manadart correct, it is not the cidr of the target subnet. See the attached screenshot in #2^ , it shows the cidr of the subnets.

[james beedy (jamesbeedy)]

I’m bootstrapping us-west-2 which is where those subnets live.

[Simon Richardson (simonrichardson)]

@jamesbeedy the image is missing/corrupt, or at least it is for me.

[james beedy (jamesbeedy)]

@mandart bootstrapping controller (the one launched from the bootstrap command above), see the subnet it landed on

[james beedy (jamesbeedy)]

@mandart my subnets in us-west-2 - I've selected the target network that I am trying to bootstrap in the sceenshot.