[2.x] MAAS not adding mtu size change to dhcpd.conf
Bug #1735207 reported by
Jeff Hillman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Mike Pontillo | ||
2.3 |
Triaged
|
High
|
Mike Pontillo |
Bug Description
When editing the MTU size for a VLAN and DHCP is enabled on that VLAN, MAAS is not adding the line
option interface-mtu <mtu size>;
to that VLAN.
Using a DHCP snippit is a work around for this, but MAAs should be performing this action when that value is changed.
In my case, I had enabled DHCP, then later altered the MTU size. I have not tested in the reverse order.
This entire issue was causing PXE to fail.
Related branches
~mpontillo/maas:add-mtu-to-ipv4-dhcpd-conf--bug-1735207
- Andres Rodriguez (community): Approve
- MAAS Lander: Approve
- MAAS Maintainers: Pending requested
-
Diff: 175 lines (+77/-4)6 files modifiedsrc/maasserver/dhcp.py (+2/-0)
src/maasserver/triggers/system.py (+10/-2)
src/maasserver/triggers/tests/test_system_listener.py (+57/-0)
src/provisioningserver/dhcp/testing/config.py (+1/-0)
src/provisioningserver/rpc/cluster.py (+4/-2)
src/provisioningserver/templates/dhcp/dhcpd.conf.template (+3/-0)
summary: |
- MAAS not adding mtu size change to dhcpd.conf + [2.x] MAAS not adding mtu size change to dhcpd.conf |
Changed in maas: | |
importance: | Undecided → High |
status: | New → Triaged |
milestone: | none → 2.4.x |
Changed in maas: | |
milestone: | 2.4.x → 2.4.0alpha1 |
Changed in maas: | |
assignee: | nobody → Mike Pontillo (mpontillo) |
Changed in maas: | |
milestone: | 2.4.0alpha1 → 2.4.0alpha2 |
Changed in maas: | |
milestone: | 2.4.0alpha2 → 2.4.0beta1 |
Changed in maas: | |
milestone: | 2.4.0beta1 → 2.4.0alpha2 |
To post a comment you must log in.
Escalating to high (has unobvious workaround)