provider/ec2: provisioning with spaces should be provider-independent
Bug #1498232 reported by
Dimiter Naydenov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Unassigned | ||
Bug Description
Currently, when a spaces constraint is given, only the EC2 provider respects this and provisions instances within the subnets of the space specified in the constraints. This needs to be done in a provider-
See related PR: https:/
| tags: | added: tech-debt |
| Changed in juju-core: | |
| milestone: | 1.26-alpha1 → 1.26-alpha2 |
| Changed in juju-core: | |
| milestone: | 1.26-alpha2 → 1.26.0 |
| Changed in juju-core: | |
| milestone: | 1.26.0 → 2.0-beta5 |
| Changed in juju-core: | |
| milestone: | 2.0-beta5 → 2.0-beta4 |
| Changed in juju-core: | |
| milestone: | 2.0-beta4 → 2.0.0 |
Revision history for this message
| Richard Harding (rharding) wrote | #1 |
| Changed in juju-core: | |
| status: | Triaged → Fix Committed |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0.0 → none |
| milestone: | none → 2.0.0 |
| Changed in juju: | |
| milestone: | 2.0.0 → 2.0-beta18 |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
We've updated to support MAAS and have plans to support future providers. Marking invalid just in that it'll be progressive improvement over time and not a single blocker for any single release.