MAAS managed DHCP should not require a router IP
Bug #1334325 reported by
James Troup
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Medium
|
Graham Binns | ||
Bug Description
With MAAS 1.5.1+bzr2269-
interface for a cluster and try and remove the router IP, MAAS
refuses, saying "That field cannot be empty (unless that interface is
'unmanaged')".
I'm not sure why this restriction exists (it's certainly not imposed
by ISC dhcpd) but it makes MAAS managed DHCP unusable for the network
I'm trying to configure as it has a MAAS private LAN and public IPs on
each server; the gateway/router is on the public IP side of each
server, not MAAS private LAN side.
Could we please make the router IP optional?
Related branches
lp:~gmb/maas/allow-blank-router-ip-bug-1334325
- Jeroen T. Vermeulen (community): Approve
-
Diff: 102 lines (+37/-3)5 files modifiedetc/maas/templates/dhcp/dhcpd.conf.template (+2/-0)
src/maasserver/models/nodegroupinterface.py (+0/-1)
src/maasserver/models/tests/test_nodegroupinterface.py (+16/-1)
src/maastesting/factory.py (+1/-1)
src/provisioningserver/dhcp/tests/test_config.py (+18/-0)
| tags: | added: canonical-is |
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| James Troup (elmo) wrote | #1 |
| tags: | added: trivial |
| Changed in maas: | |
| importance: | High → Medium |
| Changed in maas: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Graham Binns (gmb) |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Ante helpfully pointed out that there is a simple workaround which is
to edit /etc/maas/
following line:
option routers {{dhcp_
I'd still like to see this field made optional in the UI, but its no
longer a high priority (for me).