Unable to modify static address pool when no machines exist
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
High
|
Unassigned | ||
Bug Description
I would like to change the static address pool on my MAAS cluster to reduce the size of the static address pool in favour of a larger DHCP pool.
When I tried to do that, MAAS told me that the new range did not include an already-allocated static address.
* it would be helpful if it provided a list of the machines involved, like:
machine interface ip-address
machine interface ip-address
...
Nevertheless I proceeded to remove all the machines in MAAS, thinking that should eliminate any assigned addresses. But... no, I still get told that I can't change the range. Is this because there is a hidden lurking database entry for an old machine, perhaps? Or is it because the system just won't let you narrow the range at all?
Regardless, here's what I would expect to happen:
* the fact that an address is allocated to a machine can't be changed implicitly
* so the address should stay allocated to that machine
* but the range FROM WHICH NEW ALLOCATIONS happen can surely be changed
* this is true regardless of the existence of current allocations
| tags: | added: networking |
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Andres Rodriguez (andreserl) wrote | #1 |
| Changed in maas: | |
| status: | Triaged → Invalid |
| Mark Shuttleworth (sabdfl) wrote | #2 |
We believe this is no longer an issue in the latest releases of MAAS. Please upgrade to the latest version of MAAS, and If you believe this issue is still present, please re-open this bug report or file a new one.