bootstrap not respecting subnet assignment

Bug #1881431 reported by james beedy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Simon Richardson

Bug Description

$ 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

james beedy (jamesbeedy)
description: updated
Revision history for this message
Simon Richardson (simonrichardson) wrote :

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

Changed in juju:
status: New → Confirmed
importance: Undecided → High
assignee: nobody → Simon Richardson (simonrichardson)
milestone: none → 2.8.1
Changed in juju:
status: Confirmed → Fix Committed
Changed in juju:
status: Fix Committed → Fix Released
Revision history for this message
james beedy (jamesbeedy) wrote :

@manadart

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

Revision history for this message
Joseph Phillips (manadart) wrote :

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.

Revision history for this message
james beedy (jamesbeedy) wrote :

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

Revision history for this message
james beedy (jamesbeedy) wrote :

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

Revision history for this message
Simon Richardson (simonrichardson) wrote :

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

Revision history for this message
james beedy (jamesbeedy) wrote :

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

Revision history for this message
james beedy (jamesbeedy) wrote :

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.