unable to set mtu on default VLAN

Bug #1543195 reported by James Page on 2016-02-08
This bug affects 5 people
Affects Status Importance Assigned to Milestone
LaMont Jones

Bug Description

trying to set the MTU on the default vlan for a fabric fails:

{"__all__": ["Cannot modify the default VLAN for a fabric."]}

This really should work; workaround is to set mtu on all interfaces attached to the VLAN.

Related branches

Changed in maas:
status: New → Triaged
importance: Undecided → Critical
milestone: none → 1.9.1
no longer affects: maas/2.0
Changed in maas:
milestone: 1.9.1 → 2.0.0
tags: added: api networking
Dongwon Cho (dongwoncho) wrote :

It affects me too.

$ maas 1st version read
Machine-readable output follows:
    "subversion": "trusty1",
    "version": "1.9.1+bzr4543-0ubuntu1",
    "capabilities": [

$ maas 1st vlan update 0 103 mtu=9000
Machine-readable output follows:
    "name": "",
    "vid": 103,
    "mtu": 9000,
    "fabric": "fabric-0",
    "id": 5003,
    "resource_uri": "/MAAS/api/1.0/vlans/5003/"

$ maas 1st vlan update 0 0 mtu=9000
{"__all__": ["Cannot modify the default VLAN for a fabric."]}

James Page (james-page) wrote :

Interestingly on a Xenial install, if the MTU is mismatched between the vlan interface and the underlying physical network device, you hit:


Feels like either MAAS or curtin needs to figure out the right MTU settings to pass down into the install so that things all line up?

Changed in maas:
status: Triaged → Fix Committed
Mike Pontillo (mpontillo) wrote :

I feel like if you set the MTU on a VLAN within a fabric, the "default VLAN" MTU should be set to the maximum value of all VLANs within that fabric.

As discussed in the linked bug, it is not possible to have VLANs whose MTU is larger than the base interface, anyway.


Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers