Deleting a dynamic range and recreating it may fail
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Triaged
|
Low
|
Unassigned | ||
| 3.3 |
Triaged
|
Low
|
Unassigned | ||
Bug Description
I've seen some undesirable behavior that might be considered a bug. I've got a dhcp range defined for a subnet and some machines deployed using dhcp address assignments. If I delete the dynamic range and try to re-create it with the exact same start and end, it errs saying it conflicts with the hosts already allocated in the range.
You might say "don't delete the range" and mostly I'd agree except that the foundation cloud engine deletes and re-adds ranges when configuring networks.
Additionally, this problem shows up if you try to redefine the range. If you wanted to reduce the range by one IP, it again complains that there are conflicts.
Perhaps if you create a dynamic range and the conflicting IPs have all been allocated by dhcp, it shouldn't be considered a conflict.
| Björn Tillenius (bjornt) wrote | #1 |
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| milestone: | none → next |
| Jerzy Husakowski (jhusakowski) wrote | #2 |
| Changed in maas: | |
| importance: | High → Low |
| milestone: | next → 3.3.0 |
| Changed in maas: | |
| milestone: | 3.3.0 → 3.4.0 |
| Changed in maas: | |
| milestone: | 3.4.0 → 3.4.x |
Agree that this is a bug. At the very least, it should be possible to force the creation of the range, if you know that it's safe to do so.