[2.0rc1] Network model misconfigurations can silently break DHCP services

Bug #1602412 reported by Mike Pontillo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Medium
Blake Rouse

Bug Description

While doing the fix for bug #1600720, I noticed that if I added an IPv6 subnet to a VLAN attached to a rack interface which did not exist on the rack, DHCP services (for IPv4 and IPv6) went offline.

While I have proposed a fix for that specific issue[1], (so that IPv4 can now fail independently of IPv6), this is still a problem that needs more visibility. When DHCP configuration fails in this way, there is no warning or indication to the user that something is amiss. For example, when checking the service status in the rack controller details page, the DHCP services are either a green checkmark if it works, or nothing-at-all if it doesn't work.

Such a misconfiguration should alert the user in some other way, and cause the service status to change to a warning or error. Otherwise, the only indication of this problem is seeing the traceback in the log.

[1]:
https://code.launchpad.net/~mpontillo/maas/subnet-dhcp-dns-settings--bug-1600720/+merge/299754

Related branches

summary: - [2.0rc2] Network model misconfigurations can silently break DHCP
+ [2.0rc1] Network model misconfigurations can silently break DHCP
services
Revision history for this message
Mike Pontillo (mpontillo) wrote :

Looks like the upcoming work for DHCP Relay in MAAS 2.2 will fix this. (Thanks Blake!)

Changed in maas:
milestone: none → 2.2.0
assignee: nobody → Blake Rouse (blake-rouse)
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.