can't deploy to specific AWS subnets due to `juju add-subnet` fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
Encountering an issue with `juju add-subnet <space>` when trying to associate a VPC's existing subnets with network spaces. This blocks the ability to deploy a bundle to an existing VPC and specific subnets, which is important for co-existing with existing infrastructure.
Appreciate information on a workaround in the meantime (e.g. could a subnet be associated with a space by modifying the controller?). The intention is to use spaces with deployment constraints (e.g. juju deploy --constraints "instance-
Here are the error details:
```
$ juju version
2.2.2-xenial-amd64
$ juju add-space private
added space "private" with no subnets
$ juju add-subnet $SUBNET_ID private
ERROR cannot add subnet: adding subnet "10.101.1.0/24": subnet "10.101.1.0/24" already exists
ubuntu@
subnets:
10.101.1.0/24:
type: ipv4
provider-id: subnet-xxxxxxx
status: in-use
space: ""
zones:
- us-east-2b
...
```
The overall approach to deploying to existing subnets is shown in this blog, which references the approach of using spaces - https:/
tags: | added: conjure |
@Eric,
I think the syntax that worked for me was to specify subnets when creating space, something along the lines of 'juju add-space foo 172.30.4.0/24'