'juju bootstrap' into a VPC with mixed private and public subnets should pick the public subnet
Bug #1705399 reported by
John A Meinel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Expired
|
High
|
Unassigned | ||
2.2 |
Won't Fix
|
High
|
Witold Krecicki |
Bug Description
If you create a VPC with multiple Subnets in the same region, some of which have "default public address" true, and some with false. During 'bootstrap' we should be omitting the ones without public addresses as being available to use for bootstrap.
In the shared credential account, I ran into this on eu-west-1 where eu-west-1a has: 'pub-a', 'db-a', and 'a' subnets, and bootstrap selected 'db-a' which is intended to be private-only.
We can work around this with the "subnet" constraint, but we should have a better default behavior so we don't just come up and appear broken immediately.
Changed in juju: | |
assignee: | nobody → Witold Krecicki (wpk) |
description: | updated |
Changed in juju: | |
assignee: | Witold Krecicki (wpk) → nobody |
To post a comment you must log in.
@Witold Krecicki,
Have you had a chance to look at this recently?
We will not be fixing this in 2.2 as there are no further point releases planned in this series. But I wonder if we have fixed it in subsequent series.