[1.9] MAAS can auto-assign a known default gateway for a subnet to a deploying node.
Bug #1690231 reported by
David Lawson
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Mike Pontillo | ||
1.9 |
Fix Committed
|
Critical
|
Mike Pontillo | ||
2.0 |
Fix Released
|
Critical
|
Mike Pontillo |
Bug Description
It doesn't appear that MaaS 1.x has any mechanism that allows a user to reserve IPs in a subnet defined in MaaS. We discovered this after a machine was deployed accidentally with an auto-assigned IP and grabbed the default gateway IP for a subnet. It should be possible to reserve IPs within a subnet and maas should do a ping test on an IP before assigning it to a deploying node.
Related branches
lp://staging/~mpontillo/maas/auto-assigned-gateway-ip--1.9--bug-1690231
- Blake Rouse (community): Approve
-
Diff: 99 lines (+32/-3)3 files modifiedsrc/maasserver/models/interface.py (+14/-2)
src/maasserver/models/staticipaddress.py (+7/-1)
src/maasserver/models/tests/test_interface.py (+11/-0)
Changed in maas: | |
importance: | Undecided → Critical |
milestone: | none → 2.1.6 |
milestone: | 2.1.6 → 1.9.6 |
status: | New → Triaged |
assignee: | nobody → Mike Pontillo (mpontillo) |
summary: |
- MaaS does not allow reserving of IPs in subnets or check whether auto- - assigned IPs are in use + MAAS auto-assigned gateway IP, while not allowing to reserve IP's in + subnets. |
Changed in maas: | |
status: | Triaged → Fix Committed |
milestone: | 1.9.6 → none |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Setting this back to invalid provided that it is possible to reserve IP's:
https:/ /docs.ubuntu. com/maas/ 1.9/en/ static- ips#unmanaged- user-allocated- ips