Incomplete support for network spaces in Juju and MAAS
Bug #1730747 reported by
Matt Rae
This bug affects 30 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
When space name is updated in MAAS, juju reload-spaces doesn't properly update the space name in juju.
Other issues with juju space functionality:
- Editing a subnet in MAAS, for example going from 10.11.12.0/24 to 10.11.0.0/16 is not updated in juju
- Move a subnet to another space
- If an empty space is created, juju doesn't load it
- Delete space/VLAN/subnet
- "juju subnets" prints status as "in-use" for subnets where no unit/machine
is deployed, it's not clear what it means.
One potential solution could be to have MAAS lock spaces or subnets from being updated after they are in use by juju. Or notify the user if an operation in MAAS will affect deployed machines.
tags: | added: sts |
Changed in juju: | |
importance: | Undecided → High |
status: | New → Triaged |
tags: | added: maas-provider spaces |
Changed in juju: | |
milestone: | none → 2.7-beta1 |
Changed in juju: | |
milestone: | 2.7-beta1 → 2.7-rc1 |
Changed in juju: | |
milestone: | 2.7.1 → 2.7.2 |
Changed in juju: | |
milestone: | 2.7.2 → 2.7.3 |
Changed in juju: | |
milestone: | 2.7.3 → 2.7.4 |
Changed in juju: | |
milestone: | 2.7.4 → 2.7.5 |
Changed in juju: | |
milestone: | 2.7.5 → 2.7.6 |
Changed in juju: | |
milestone: | 2.7.6 → 2.9-beta1 |
Changed in juju: | |
assignee: | Simon Richardson (simonrichardson) → nobody |
Changed in juju: | |
milestone: | 2.9-beta1 → 2.9-rc1 |
summary: |
- incomplete support for spaces in juju and maas + Incomplete support for network spaces in Juju and MAAS |
To post a comment you must log in.
There are improvements in this area in 2.7 but not all the cases identified are fixed. I'm going to bump it to carry it forward.